[development] SQLite and Drupal 7
mathews.kyle at gmail.com
Tue Feb 3 18:51:50 UTC 2009
A thought as well -- install profiles could ship with an sqllite db with all
the customized site configuration. Then as part of the regular installation,
the info from that db would be copied to the regular mysql db.
eBusiness Center @ BYU
On Tue, Feb 3, 2009 at 11:29 AM, Larry Garfield <larry at garfieldtech.com>wrote:
> On Tue, 03 Feb 2009 10:09:11 -0500, Syscrusher <syscrusher at 4th.com> wrote:
> > On Mon, 2009-02-02 at 22:39 -0600, Larry Garfield wrote:
> >> > 4) Should I just shut up and go back into my corner?
> >> Of course not. :-P
> > Heartily agreed. Whether or not we adopt chx's suggestions, it is an
> > idea worthy of discussion.
> > Having a read-only initial conditions database in SQLite also offers us
> > the potential for an administrative "reset entire site to defaults"
> > option, which could reset all settings but not delete nodes or users (or
> > could offer the admin the option of these two things). This would be a
> > great last-resort recovery option for confused novices, and it would be
> > a fine testing aid for us developers.
> > I am not yet ready to say +1 to adopting chx's suggestion, but I'm ready
> > to say +1 for discussing it seriously.
> > Scott
> To clarify, I am not against an SQLite DB as a "Safe mode" fallback, or as
> an install mechanism. Those are both definitely worth considering. It's
> making a secondary DB required for normal operation that I do not believe is
> a good idea.
> --Larry Garfield
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development