On 2/13/18, Chris Brody <chris.br...@gmail.com> wrote: > - Does this imply that a SQLite database may be left in some kind of > unrecoverable, corrupted, or otherwise invalid state in case an > application would terminate without calling sqlite3_close() on all > open database connections?
No. The database might be left in a weird state, but it will automatically recover the next time you or any other process opens the database. Unless, that is, you try to get clever and delete the *-journal or *-wal file or do something else that interferes with the automatic recovery process. If you delete the information that SQLite needs to recover then it won't, and the database will be left in its weird state, which is now considered corrupt. Do not do any of the bad things listed under https://www.sqlite.org/howtocorrupt.html and you will be fine. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
