Simon Slavin-3 wrote > When you lose data are you ever losing part of a transaction ? SQLite is > allowed to lose entire transactions, back to some END/COMMIT statement. > It should not be losing parts of transactions. Or, at least, when you > reopen the database using the SQLite library it should restore the data to > an END/COMMIT statement.
Thanks a lot guys! This really helps. I'll try out the user_version trick. To answer your question, Simon - no, I've never seen it losing part of a transaction - only whole ones. This is just durability loss - the COMMIT call returned, but after crash & restart, an entire transaction is reversed and it's back to the point of the COMMIT before that. I still much rather make the tradeoff for occasional whole transaction losses instead of running WAL/FULL, as long as I have a way to manually force a sync at critical times. -- View this message in context: http://sqlite.1065341.n5.nabble.com/Forcing-a-manual-fsync-in-WAL-NORMAL-mode-tp78260p78299.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
