On 02/08/2011 10:24 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 14:51 >> To: sqlite-users@sqlite.org >> Subject: Re: [sqlite] database disk image is malformed 3.7.x >> > >> 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. > > Hi Dan, > > The tool shows me the SQLite version of the test.db3 is indeed 3007004. > So the database created with version 3.6.23.1, is once modified with a > 3.7.4 and then modified with 3.6.23.1 again. > > So I guess we run into something similar to this ticket; > http://www.sqlite.org/src/info/51ae9cad317a1 . > > One strange thing though, I also have a database with version 3007002 > which does not experience the database corruption. Can it be that the > size just matches accidentally for that database?
The only problem we know of was caused by 3.7.0, which was replaced by 3.7.0.1 when the problem was discovered. Even with 3.7.0, you needed the right sequence of writes from 3.7.0 and some earlier version. I don't know how the corruption you're seeing is caused. I would like to though. Do you use auto-vacuum mode? Or incremental vacuum? Dan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
