> On 6 Feb 2004, at 14:05, D. Richard Hipp wrote: > > > 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. > > 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.
My understanding is that SQLite has had this auto-update feature since version 2.6.0. If I understand correctly, you should only have a problem if you are *now* using a version prior to that, and go from that version directly to 2.8.12 or later. If you've kept your version of the db engine current, or at least have upgraded to 2.6.0 or later, then all of your databases should now have their indices updated by now. Have I misinterpreted something? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
