On 01/12/13 06:10, L. Wood wrote: > D. Richard Hipp, are there any plans to make this more robust in the > future, so reading/writing a corrupt database (with no -journal file > available) will return an *error* instead of causing further damage?
There has been a ticket languishing for many years to at least make detecting a mismatch between the database and a (possibly non-existent) journal possible: https://www.sqlite.org/src/tktview?name=61d35ac210 Roger _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
