On 02/08/2011 08:26 PM, Dennis Geldhof wrote: >> -----Original Message----- >> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- >> boun...@sqlite.org] On Behalf Of Dan Kennedy >> Sent: dinsdag 8 februari 2011 12:33 >> To: sqlite-users@sqlite.org >> Subject: Re: [sqlite] database disk image is malformed 3.7.x >> > >> We're very interested in how this happened. Do you ever write to the >> db using the 3.7.4 tools? Or write to it with any other 3.7.X version? > > I have several machines over here (with developers) and the corruption > only occurs on some machines. Besides that I am not able to reproduce > this issue with a brand new database (maybe because my tools are at > version 3.7.4). I can only reproduce this issue on some of the database > that are in use more than 2 months. Looking at the description you gave > and the symptoms we have, maybe this is caused by issue; > http://www.sqlite.org/src/info/51ae9cad317a1 . Because the > System.Data.Sqlite wrapper is still at sqlite version 3.6.23.1 and the > tools update automatically we could have triggered that issue. > Is there a way to check if the database was ever opened with a sqlite > version newer than 3.6.23.1, so we can make sure it was ever edited by a > tool?
Grab the C file from this link and compile it to a standalone executable. http://www.sqlite.org/src/raw/tool/showdb.c?name=471c0f8fa472e71bb7654500096a5bdb4ea1fb2a Then run the resulting executable with the path to a database file as the first argument and "dbheader" as the second. i.e. ./showdb test.db dbheader where "test.db" is the database file name. The program prints out a short report that, if the database was ever written by 3.7.0 or newer, includes the version number of the most recent version to do so. Dan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
