> Nope. If there was a problem in closing down they can hang around (which is > their whole point for recovery). Also if a journal mode of "persit" was > used. But mostly from incorrect closure. > > So check for any -journal, -wal, or -shm files of the same name if you want > to obliterate a database. > (Am I missing any others?)
Is there a minimal work example (in software way but not hardware failure way) to make these extra files stick around upon closing a sqlite3 session so that I can have a proper test case to make sure I always delete them? Thanks. -- Regards, Peng _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
