[development] SQLite and Drupal 7 -- let's try this again
Stewart Robinson
stewsnooze at gmail.com
Wed Feb 4 11:37:45 UTC 2009
Also commercial support of SQLite is sparse. I mailed my hosting provider
and they won't support SQLite and have no plans to. They'll let us use it
but won't own it. All of my websites live under a managed service agreement
so that the hosting company can simply look after them. This could be a
step in the wrong direction for corporate adoption if SQLite is forced.
Stew
On Wed, Feb 4, 2009 at 11:05 AM, Ashraf Amayreh <mistknight at gmail.com>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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20090204/e12dc7c1/attachment-0001.htm
More information about the development
mailing list