"Michael P. Soulier" <[EMAIL PROTECTED]> writes: > Hello, > > I just got a nasty surprise. I installed an sqlite 3.3.5 .dll on windows with > pysqlite2, and I used an application to create a database file. I then scp'd > the file home to my linux box where I have sqlite 3.2.2 installed, and I got > this: > > sqlite> .tables > Error: unsupported file format > > Ouch. I'm building 3.3.5 now but it puts a kink in some of my cross platform > development plans. > > How often is backwards compatibility to be broken in this way?
Actually, that's not backwards compatibility you're looking for, it's forwards compatibility. You want a new database to be readable by the old version that knows nothing of the new format. If you take your database from 3.2.2 and use it with 3.3.5, it'll work fine. The reverse is not true, however, and forcing it to be true would mean never being able to add new features. If you look at the docs, I believe there is a way to tell 3.3.5 to generate the old-style database if that's really what you're looking to do. Derrell
