Nothing is definite yet, but we are looking into the possibility of releasing SQLite version 3.2 in a few weeks. Version 3.2 will include a subtle but important file format change that will break forwards compatibility. That is, Version 3.2 will be able to read and write files generated by 3.0 and 3.1. But 3.0 and 3.1 will not be able to read and write files generated by version 3.2.
Again, this is not definite yet. But if we chose to go this route, a beta release of version 3.2 will appear real soon - probably the first part of March. The changes will be very minor and will not effect stability of the library - we might skip beta all together and go straight to stable. The file format change is to be used in a new CREATE TABLE ADD COLUMN statement. Actually, the incompatibility probably will not be as bad as described above. We will likely rig it so that files generated by version 3.2 will be readable and writable by version 3.1 and 3.0 as long as you never do an ALTER TABLE ADD COLUMN. The first time you do do an ADD COLUMN, the database will become unreadable by 3.1 and 3.0 until after you VACUUM. So, if you are using SQLite in a product and can wait a couple of weeks before you lock into a particular version, that would be a good idea. -- D. Richard Hipp <[EMAIL PROTECTED]>
