Roger Binns wrote: > Going back to Joshua's original question, by default a SQLite database is > not read-only even if you think it is. The major reason is that even if you > wanted to use it read-only, the previous program may have had it open for > writing, and may have crashed in the middle of a transaction. Consequently > the reader needs to fix the database using the journal to get it back into a > correct state which involves writing. Heck even while you have it open and > idle, a writer could have started a transaction and crashed requiring > recovery.
I think that it should be possible to configure SQLite to be strictly read-only in every respect, such that if with such configuration SQLite is told to open a database that would need updating from a journal or WAL, it would fail with some appropriate error rather than fixing the database. This in contrast to the approach of apply the journal or WAL and then don't change anything further; the latter is also important to support but users should have a choice between the two options. -- Darren Duncan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
