I have an application using sqlite v. 3.2.1. This application is storing
some extremly important data in this database. Yesterday I received the
SQLITE_CORRUPT error message. This happened on a test system so it is not
that bad, but I am now very nervous about this happening in my production
system. Is this a common problem with sqlite? If it is, please tell me
because I need to switch to another database then. Is there some known bug
which can cause this? The version I am using is starting to get old, and I
can upgrade to the newest one, but will it help? Will I then be guaranteed
that this will not happen again. I am 100% sure there is no other process
writing to the database file. My application is written in C++ using the
CppSqlite sqlite wrapper. The application is single-threaded. I am using
Debian-Sarge. The PRAGMA integrity_check shows me this: *** in database main
***
Page 2: initPage() returns error code 11. Can somebody help?

Reply via email to