Dear Simon, I am a little worried with your last post because, I must admint that I do not take special measures in my application when such errors occur to guarantee that no more DB access are performed.
I have thus the following questions : 1. What would be the proper reaction to SQLITE_FULL, SQLITE_IOERR, SQLITE_CANTOPEN ? Perform a sqlite3_close ? Just exit the program as is without touching the database file descriptor ? And once the program has left, can we perform a sqlite3_open ? 2. What is the exhaustive list of error codes that shall be considered as fatal ? 3. Is it documented somewhere ? Thanks in advance, Brice 2016-01-14 11:41 GMT+01:00 Simon Slavin <slavins at bigfraud.org>: > > On 14 Jan 2016, at 9:58am, sanhua.zh <sanhua.zh at foxmail.com> wrote: > > > Through the error code timeline, it shows that much of SQLITE_FULL, > SQLITE_IOERR, SQLITE_CANTOPEN happened before SQLITE_CORRUPT. > > You should never get to this situation. The three result codes > SQLITE_FULL, SQLITE_IOERR, SQLITE_CANTOPEN are fatal errors. Your program > should crash there, it must not try to continue using the database. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
