[feature] Table prefixes for projects specific tables

Project:      Drupal
Version:      4.3.2
Component:    other
Category:     feature requests
Priority:     normal
Assigned to:  Anonymous
Reported by:  magico
Updated by:   adrian
Status:       active

I agree with the concept. 

although i wonder how much this might affect upgrade paths.

+1

adrian



Previous comments:
------------------------------------------------------------------------

February 26, 2004 - 11:59 : magico

Just to know what you think about this possible organization task. It's
a decision from the module author to or not to use table prefixes for
it's module specific tables. Anyway I think that this should be a rule,
because this way it's easier to do database administration and
organization.

For example (ecommerce):
address -> ec_address
cart -> ec_cart
...

------------------------------------------------------------------------

February 26, 2004 - 14:06 : jhriggs

I _completely_ agree.  Modules' tables should be prefixed with the
module name just like its functions (at least for contribs, but it
would be nice for core/system tables too).  I have done this in all my
modules (i.e. tables quotes_quotes, menus_items, etc.).  We are just
asking for name collision as more modules are developed.  Plus, it
makes it much clearer what "owns" a table.  From an administration
point-of-view, I think this is a must.

+10

--
View: http://drupal.org/node/view/6069
Edit: http://drupal.org/project/comments/add/6069