Thank you. It appears I misunderstood how rollback journals were operating.
As a follow-up, when exactly does the rollback journal get deleted? Is there a period of time where the database itself could be in a consistent state and a rollback journal could exist containing data no longer in the consistent database? Is this the scenario after successfully committing a transaction but before the rollback journal is deleted (database contains the newly committed records while the rollback journal contains the old, now overwritten, pages) ? Thanks. Bryan -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp Sent: Friday, February 17, 2012 2:59 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Prepare SQL for Read-Only Database with Journal File On Fri, Feb 17, 2012 at 2:45 PM, Angelo, Bryan [USA] <angelo_br...@bah.com>wrote: > All, > > I am using SQLite version 3.7.8. I am receiving the SQLITE_IOERR result > code from sqlite3_prepare_v2 function when attempting to compile a PRAGMA > statement on a read-only database where a rollback journal file also > exists. Is it possible to force SQLite to ignore rollback journal files > (or WAL files) ? > If you have a hot journal (a rollback journal that still exists and has a non-zero header) that indicates that the previous process to write to the database did not shutdown cleanly. The journal must be rolled back in order to restore the database to a consistent state. SQLite is not able to read the database until it has been recovered by rolling back the hot journal. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
