I'm the author of a small Windows application that embeds SQLite. I'm currently using version 3.5.9 with PRAGMA locking_mode = EXCLUSIVE and PRAGMA journal_mode = TRUNCATE. I just received a crash report from a user with the dreaded error: "database disk image is malformed".
My application is multi-threaded, although only the main thread calls SQLite functions (the other threads do non-DB stuff). I have read http://www.sqlite.org/lockingv3.html#how_to_corrupt, so I know the database can become corrupt if someone deletes the journal, if hardware is faulty, or the OS is faulty. Are there any other known ways that the database might become corrupt? Any suggestions for how I might pinpoint the cause of the corruption? Is there anything I can do to make my usage of the database more robust? (aside from making backups of the database, which I will now likely implement) -- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
