On Wed, Feb 07, 2007 at 08:40:00AM -0500, James Carlson wrote: > This means you're going to need a way to read and manipulate a > repository that's at least two releases old and store items in the > repository that are relevant for things at least two releases in the > future.
This makes it difficult to commit to a repository format, yes. Sticking with SQLite 2 forever is one option. Switching to SQLite3 should be possible because the two APIs don't share any symbols and can be used concurrently in the same program, but because SQLite3 is still undergoing development it's difficult to meet this requirement with it. Since new SQLite3 releases can always read older SQLite3 databases (the SQLite community works very hard to make this possibl) one possibility would be to always save a dump of the repository when manipulating a dead root and load this on boot. I.e., use SQL as an intermediate step. This would have the benefit of making it possible to switch from using SQLite to other SQL-based databases. Nico --
