On Wednesday, 4 September, 2019 11:22, Peng Yu <pengyu...@gmail.com> wrote:
>> If you delete the database file then make sure you also delete any other >> files that might have been associated with it, such as left over journals >> and so forth. >I never see those extra files in practice. Are they guaranteed to be >deleted automatically once an SQLite session is finished? They are deleted when the last connection to a database is closed by an sqlite3_close() call. Unless of course the program requests they stick around. And of course you can never guarantee that the CPU will not be hit by a stray dark-matter particle causing a program to abort without cleaning itself up, or that the power will never fail, or any of a number of other reasons that those extra files might be present. Do you want to accept the risk thst you will have to travel to fix something that is broken at 2:30 in the morning in the middle of a holiday while you are busy making sex on the beach when you could have with just a little tiny bit of aforethough avoided that inconvenience altogether? Then again, perhaps I am just lazy and prefer things that "just work". -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
