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

Sam Tresler sam at treslerdesigns.com
Wed Feb 4 15:01:57 UTC 2009

If I understand chx correctly having the database in a deployable file
would make installation even smoother AND install profiles would be able
to come 'fully deployed' as all the modules will have been already set
up in the system table.  This isn't really a huge performance increase
(although, a file read is faster than a db query).  It will make
deploying from staging a little trickier in multi server environments. 


chx correct me if I am wrong, but are those the main goals of this?

On Wed, 2009-02-04 at 13:05 +0200, Ashraf Amayreh wrote:
> Trying my best to understand the benefits of this. What benefits are
> to be gained from moving these tables to an SQLite database?
> Performance improvements? Does it ease anything for developers? What
> exactly are the pros and cons? Whatever they are, they just don't hit
> me as intuitive.
> On Wed, Feb 4, 2009 at 12:41 PM, Robert Douglass <rob at robshouse.net>
> wrote:
>         chx, are there also implications for how one would deploy
>         sites in your suggestion? Would it make it easier or harder to
>         move stuff from staging to production, for example? I'm
>         fascinated by your idea and think that if it can be made an
>         optional requirement (yes intentional wording), then it could
>         be very interesting. I encourage people to keep asking
>         questions until they understand the full idea, because so far
>         I think a lot of people essentially stopped reading at "Should
>         we require SQLite?"
>         -Robert
> -- 
> Ashraf Amayreh
> http://aamayreh.org

More information about the development mailing list