On Fri, Jan 21, 2011 at 5:33 PM, Pavel Ivanov <[email protected]> wrote: >> (2) Are there any changes that can/should be made >> to sqlite3 so that it can identify the bogus journal in this >> scenario and discard it? > > Define the word "bogus". How should SQLite understand that the journal > and the database are unrelated?
I've wondered in the past if a db cookie couldn't be added, which has to match the cookie in the primary database. Even better if it could change over commits so that one could tell if the journal mis-matches because the database file was restored from backup or something. Unfortunately, I never was able to work my way around legitimate mis-matches (where the page the db's cookie is derived from went awry). -scott _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
