Hi all, I write an SQLite browser for macs, and someone recently brought to my attention that it doesn't handle corrupt database files very well. I've read the pages on pragmas for integrity checking and how locking problems can cause corruption, but am looking for something a bit different:
1. Are there detectably different ways for a database to become corrupt? Or is SQLITE_CORRUPT the only one? 2. Is there an easy way for me to create a couple of corrupt databases for testing? I was thinking that opening a database file in a text editor and swapping bits around would do it, but wondered if this would produce different symptoms than a file 'properly' corrupted through accidental damage. Thanks, Ben Barnett _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
