If you use a modern version of SQLite (version 2.6.0 through 2.8.11) to open an older database file (version 2.1.0 through 2.5.6) the library will automatically rebuild all the indices in the database in order to correct a design flaw in the older database files.
I am proposing to drop support for this auto-update feature. Beginning with 2.8.12, if you attempt to open a database file built using version 2.5.6 or earlier, the open attempt will fail (with an appropriate error message). You will have to update the database file manually.
Would this proposed change cause anyone unreasonable hardship?
I can see both sides of this. On the one hand I'm a *big* supporter of keeping SQLite small, but on the other hand I have a project with currently over 50,000 sqlite databases on a large (terabyte) filesystem. Upgrading each one with a utility (and the associated downtime) would be a bit of a nightmare. Upgrading them on a per-access basis like the current implementation would do is a bit more agreeable to me.
Tough choice.
Matt.
________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
