On 23 Jun 2016, at 11:13pm, Jim Borden <jim.bor...@couchbase.com> wrote:
> From what I have read, error 11 is extremely hard to cause through library > usage alone. The key offences seem to be: > > 1) Using two versions of SQLite at once in an application > 2) Bad OS file locking > 3) A rogue process writing garbage into the file Two possibilities missing from the above list: 4) A rogue process writing garbage into memory SQLite thinks it owns 5) Hardware fault Problem (1) is not quite right. Apart from a couple of very obscure versions here's no problem with different versions of SQLite. The problem is for one application to be using two SQLite libraries at once, even if they are the same version. It's difficult to do this accidentally. As for investigating the problem, I can only suggest something drastic: Run "PRAGMA quick_check" after every command which makes any change to the database and trigger an immediate crash if it fails. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
