On Thu, 20 Apr 2006, Steve Bland wrote: > We have been using SQLite ( v2.8.6 ) for a while now and as part of a > new release were thinking of moving ahead to a more current version. > > But that is where the issues began. I did search the archives, but found > noting of any real use on this. The same with the faq page and the > changes page. Naturally I could have missed something but... > > If I try to load one of our existing files with the command line tool, I > get the response "Error: file is encrypted or is not a database". If I > do a read command on the same file, I get "Incomplete SQL: ** This file > contains an SQLite 2.1 database **" and then there is incomplete and > rather odd SQL data. The 2.1 database message actually overwrites the > SQL on the screen.
The file format changed with SQLite 3.x. This was to allow certain improvements (such as blobs, 64bit integers etc) that wearn't possible with the SQLite 2.1 based format. > > If I load these files with v2.8.17 all is fine. Is there a compatibility > problem? Is there an import tool? You can export data from v2.8.17 using .dump, and read in the SQL commands from the dump to a 3.x database. However, the SQLite 3 API is also different, so unless you're using a wrapper, it might just be easier to stay with 2.8 unless you want some of the new functionality from 3.x. > > I know this is probably covered in either the email digests or somewhere > on the site, but I could not find any information. http://www.sqlite.org/version3.html > > > Steve > -- /"\ \ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \
