On Mon, Aug 12, 2013 at 7:17 AM, Jan Slodicka <j...@resco.net> wrote:
> From time to time we receive user reports about database crashes. Problems > seem to be iOS-related. (Given the number of reports it would be a > coincidence if other platforms worked flawlessly.) > > Our testers finally managed to hit the problem, so I have a corrupted DB > file. On the other hand, that's all I have as the problem is not > reproducible. > Has anybody any clue what can go wrong? I can add more details if usefull > or > even send corrupted DB. (Just will have to convert it to plaintext, > hopefully this does not create other problems.) > All that the "integrity_check" output says is that the database file is corrupt and that the corruption is restricted to indices, so that it can be completely repaired by running "REINDEX". Though, the fact that the corruption is restricted to an index is probably a coincidence. Ideas about what might be causing this are all listed in http://www.sqlite.org/howtocorrupt.html -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
