It seems I need to make sure that Drupal can pull together itself enough to rebuild the missing SQLite database by copying the tables from MySQL. And then reload itself in a useable state. This means that actually deploy is a lot lot easier than I originally thought.
Yep, that'd be great. But, I'm still iffy on REQUIRING SQLite. I'd be a lot happier if it was a non-interactive *optional* thing. * If SQLite is built into PHP, use it (so, you'd do your function exists around relevant pieces of code). Anything we continue to build will have to support reading from MySQL in the absence of. This would also stop all the whiners who are complaining about SQLite without actually understanding the point of it (as well as the *very real* lack of support for SQLite in some hosting environments). * Since it's a cache, it should probably end up in files/db, similarly to files/css and files/js. Likewise, that means it should also be deleted when one Clears the cache under the Performance page in admin. This, along with your "rebuild when it disappears" change, would allow me to continue to do my MySQL {system} modifications without the cache getting too heavily in the way. -- Morbus Iff ( if god is my witness, god must be blind ) Technical: http://www.oreillynet.com/pub/au/779 Enjoy: http://www.disobey.com/ and http://www.videounderbelly.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus