On Sun, Dec 1, 2013 at 9:10 AM, L. Wood <lwoo...@live.com> wrote: > This makes sense now, thanks. > > 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? > > One idea: A "flag" could be added to the main database file to indicate > that it has a corresponding -journal file. If it has the flag but no > -journal file exists, that would be an error. To add the flag, Mac OS X has > extended attributes. Not necessarily available on all filesystems, but a > nice protection against corruption where available. > > What do you think? Possible? Impossible? >
Not possible. Doing any writes to the database file (such as to set a flag) requires a journal file, otherwise a power loss in the middle of the write can cause database corruption. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
