-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/02/12 10:59, Korey Calmettes wrote: > If I do happen to recreate the problem, is there a way to track the > location in the file that the corruption begins and how long the > corruption is?
Recreating the problem is the hard part since something isn't working the way it should. You can make very frequent copies of the database plus frequent runs of pragma integrity check. If it is a bug in SQLite (extremely unlikely) then the corruption should be deterministic so the information needed is how to reproduce. If it is an issue with other code corrupting memory then using valgrind is a good idea. If it is an OS/hard drive kind of issue then the corruption will be more random each time due to other system activity. In this case there is nothing SQLite can do. You may want to read this page covering the SQLite file format which will give you a better idea of how things are laid out: http://www.sqlite.org/fileformat2.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8q5jMACgkQmOOfHg372QS1OACglvP9r9q/b9dSt0L0GSz5UbzB vvkAn0gwNsqjATtALH0zaOFKnxjH0SqB =5IfV -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
