On Wed, Jun 18, 2008 at 10:39 AM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Jun 18, 2008, at 10:25 AM, Stefan Arentz wrote: > >> The documentation has the following about the OFF setting of >> JOURNAL_MODE: >> >> "The OFF journaling mode disables the rollback journal completely. No >> rollback journal is ever created and hence there is never a rollback >> journal to delete. The OFF journaling mode disables the atomic commit >> and rollback capabilities of SQLite. If a crash or power failure >> occurs in the middle of a transaction when the OFF journaling mode is >> set, then the database file will very likely go corrupt." >> >> I wonder what 'corrupt' means here. >> >> Does it mean corrupt as in 'the internal low-level database structure >> will likely go corrupt' or does it mean 'the data in the database will >> likely go inconsistent'. >> > > Both. Your database will likely be unusable. Do not set > journal_mode=OFF on any database that you cannot recreate in its > entirety from secondary data following a program crash.
Thanks Richard, that is exactly the answer that I needed :-) S. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
