Hi, I have using Sqlite for my small embedded projects for quite a while. Recently we found a condition where is simple select all does not operate properly. Problem is incorrect journal file, which is created on system reboot. Reproduce this condition relativity simple:
step 1: we open db step 2: write/update something to db. step 3: switch journal to memory step 4: write/update something to db. Do not close you SW keep it running and DB open step 5: reboot your system or kill you SW not gracefully. This reboot/kill will dump incorrect incorrect journal file to the file system. This will corrupt DB on next start. I am using simple workaround: switch journal to memory before any other db access. I will rebuild sqlite with journal to memory by default later. This is reproduced very stable from 3.7.5 to latest release. And I do not test multiple switching journal file/memory with update db between switching. I do not need fix for this. Just was thinking you would like to know about this problem. I appreciate what you are doing with this SW. Andrei _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
