[development] SQLite and Drupal 7 -- let's try this again

Jakob Petsovits jpetso at gmx.at
Wed Feb 4 07:49:47 UTC 2009

On Wednesday 04 February 2009, Karoly Negyesi wrote:
> If we put these tables in an SQLite table then the only time this file
> changes is when your code changes. Therefore, when people with high
> performance sites deploy their new code, they can deploy the new
> database. There is no new procedure to be created, just one more file
> added to the roster.
> Now, if I ask this way, are people still against putting registry and
> system into an SQLite database?

If settings.php just specifies the SQLite file for the system and registry 
tables, and the MySQL database for the other tables, wouldn't that solve the 
issue and make it an optional feature for people who want this?

Or is there something more to be gained by hardcoding SQLite access?


More information about the development mailing list