Hello, thanks for the replies!
A sample Mountain-unreadable file is here: http://www.superflexible.com/broken.sql Works fine under Snow Leopard. I get the same results when using my own application as when using /usr/bin/sqlite3. So, we can concentrate on the sqlite3 command line tool. I noticed that with the new sqlite version, I can no longer use the CONSTRAINT keyword. In other words, in a CREATE TABLE script, I had to change this: CONSTRAINT PK_SECTIONS PRIMARY KEY (ID), to this: PRIMARY KEY (ID), And the new sqlite version can't read the old sqlite files. But there may be more to it. And pragma integrity_check reports: Error: malformed database schema (DATA) - near "CONSTRAINT": syntax error And a .dump results in an incomplete dump, otherwise it would be easy for me to convert/fix the database. The .dump does not give me any of the contents of the table DATA. Cheers, Tobias > On 3 Aug 2012, at 3:33pm, Tobias Giesen <tobiasgie...@gmail.com> wrote: > > > I have one particular type of database that has become unreadable on > > the new Mac OS 10.8. It must be related to the SQL structure. The error > > I get is "database disk image is malformed". But the same file, on > > Snow Leopard, works fine. > > > > The SQLite version on Snow Leopard is 3.6.12, and on Mountain Lion it > > is 3.7.12. > > How are you accessing this file ? Are you using your own application or are > you using the shell tool included with Mac OS X in > > /usr/bin/sqlite3 > > ? In the folder where you find the database file on your 10.7 computer, are > there any other files with similar names ? They may be journal files for > when the database was not closed properly. > > > The strange thing is, when I attempt to load the sqlite3.dylib from > > Snow Leopard under Mountain Lion, it also does not work. But I'm not > > totally sure if loading the older sqlite3 library actually worked. > > That may be totally unrelated to the file format. You may be trying to open > the wrong dynamic library, or one compiled for a different OS, or something. > Check out the database itself using the shell tool, then involve a dynamic > library only once you're sure the database file is okay. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
