That should be safe too. I hope someone else can help debug your problem.
Many bugs like the one you mentioned are a result of
a) having other parts of your program misuse SQLite file handles
b) having other parts of your program overwrite memory SQLite is using
c) using file storage mounted across a network with buggy network systems
Maybe that will help.
Thanks.. Was just checking with Valgrind but it didn't show anything weird.
I figured out an easy way to check the contents of a WAL file though. I
copy either just the database file or both database+wal and then open
with the cli and check the data with sql select. The experimentation
showed that the problem I'm having doesn't seem to be (at least not
directly) related to the contents in the wal file.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
