I noticed this bug fix in 3.5.7: - Store the statement journal in the temporary file directory instead of colocated with the database file.
This seems fraught. Aren't temporary directories routinely purged? If you get unlucky and the temp directory is purged immediately after you reboot, then your DB will be corrupt. It also makes it much harder to debug issues on clients' machines, because you can no longer just say "send me all the files in the folder yadayada..." 2008/9/25 Jeffrey Rennie (レニー） <[EMAIL PROTECTED]> > Small correction: I'm using sqlite version 3.5.9. > > > On Thu, Sep 25, 2008 at 1:08 PM, Jeffrey Rennie (レニー） <[EMAIL > PROTECTED]>wrote: > >> I'm seeing this happen on Mac OS X, after the user hard reboots his >> computer. I'm compiling with -DHAVE_FULLFSYNC=1 and running with PRAGMA >> synchronous = 2. >> >> Is there anything else I should set to avoid this? I'm using >> sqlite3.3.4. Has this bug been fixed in a more recent version? >> >> Sincerely, >> Jeffrey Rennie >> > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
