Hi, I encounter the same issue as described here: https://www.mail-archive.com/sqlite-users%40sqlite.org/msg57092.html usually once or twice a day, when running a performance test-suite for my application (using SQLite 3.8.1).
What is the correct way to handle the SQLITE_PROTOCOL errors that usually occur when using WAL databases from multiple processes? If I retry the query (or run other queries) after an SQLITE_PROTOCOL error is it possible to get the database corrupted, like it used to be the case with SQLITE_BUSY? (https://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError) I tend to think that the only safe way is to just close the database and quit the application when I encounter an SQLITE_PROTOCOL error. Thanks, --Edwin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
