I think you have answered your own question. If you use synchronous=off, you are saying "I don't care much about this database." When you "save" documents, you are merely putting them in a computer's cache (memory) and then confirming to the user that they are on the hard drive, when they aren't necessarily there.
So, user clicks Save, program says it saved it, user turns off computer, database is corrupt. Don't know why this would happen all of a sudden, unless maybe they upgraded their OS and it has decided to cache volatile data longer to increase performance at the expense of data integrity. I hope you're able to rescue your data. Someone else mentioned on this list a while back that they could recover their data by doing retrieval based on rowid: do a select * where rowid=1, then 2, then 3, etc. until you get a failure. Once you get a failure, the rest is lost. Good luck, Jim On 5/15/09, Kevin Gale <kev...@transeomedia.com> wrote: ... > 4. synchronous is OFF (we have stopped setting this in the new build of our > app). -- Software first. Software lasts! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
