chx: Was your basic idea to isolate the more static parts of the database from the more active parts? It strikes me that could be done without SQLite. On Tue, Feb 3, 2009 at 4:32 PM, Sam Tresler <sam@treslerdesigns.com> wrote:
On Mon, 2009-02-02 at 20:14 -0800, Karoly Negyesi wrote:
We could say that for high performance sites you only change system or the registry when you deploy and thus the SQLite file is just one more to be deployed.
This is not a viable solution for content heavy sites such as newpapers and radio stations. If I understand it correctly it would involve pausing the entire content creation staff while development pushed the new db file live.
It would also entail having site admins, that might not be administrators required to either know what was a safe change in a clustered environment and what wasn't, or attempting to restrict the access of site-admins in complex ways.
I'm not shut off to the idea, but I don't see it working well in a clustered environment.
-Sam Tresler