[development] Separating configuration vs data tables

Adrian Rossouw adrian at bryght.com
Sat Jun 10 12:12:19 UTC 2006

On 10 Jun 2006, at 4:27 AM, Chris Johnson wrote:

> Instead, I suggest the switch code between "content" and  
> "configuration" tables be smart enough to select either separate  
> Postgres schema, separate MySQL databases, OR different *table  
> prefixes*.  The one could have the same advantages with all tables  
> in one database.  The biggest drawback to this scheme is the  
> existing problem with prefixes:  the install scripts (and update  
> scripts?  or is that fixed?) are not able to handle prefixes in an  
> easy and automated way.  It takes hand editing by someone with a  
> clue about SQL.
not with the install patch that is being proposed for core.

it wraps the drupal schema in a system.install, and uses db_query  
with the {} to create the tables.

Also. all contrib modules should be prefix friendly.
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com

More information about the development mailing list