This is my table, I just wanted to show the error that it is throwing. Is the error due to /tmp being full on my device ? Further debugging at our end showed that one way to replicate the problem is to remove the hot journal file in the middle of an insert transaction but we are not sure if that is the actual cause of the problem or not.
In the application, we have a logic to check the db file size and if it grows beyond a certain threshold, we would take a backup of the db file. But once we do the delete-the journal-in-the middle-of-a-transaction operation, this size check never passes and the db size keeps on growing. Why could that be ? -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
