On Jun 08, 2006, at 18:20 UTC, [EMAIL PROTECTED] wrote:
> See section 6.0 at http://www.sqlite.org/lockingv3.html
Thanks. Nothing there obviously applies in this case -- there was no power
failure, and no files were moved or deleted as far as I'm aware -- but these
are good tips to keep in mind anyway. It's possible that it was just some
random bit flip; it was buggers hot here yesterday.
I also occasionally back up the database using subversion ("svn commit"), while
the app that uses it is still running. My belief is that subversion only reads
a file to commit it, and doesn't write to it, but it's possible that is wrong.
Thanks to the backup, I only lost about a day's worth of data, and much of that
was recoverable from other sources. It sounds like corruption is fairly rare,
so for now I'll just bolster my backup & recovery procedures and stick with it.
Thanks,
- Joe
P.S. My apologies for the double posting -- I thought the first one had gotten
lost because it was sent too quickly after I joined the list.
--
Joe Strout -- [EMAIL PROTECTED]
Verified Express, LLC "Making the Internet a Better Place"
http://www.verex.com/
