OK. Manual crash might be a kind of solution.
BTW, how does SQLITE_FULL finally result in SQLITE_CORRUPT? How does it happen in detail? ???? ???:Simon Slavinslavins at bigfraud.org ???:SQLite mailing listsqlite-users at mailinglists.sqlite.org ????:2016?1?14?(??)?18:41 ??:Re: [sqlite] Database Corrupt While Disk Full 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
