I may have missed this already being discussed. Will you have access to a copy of the database as it was before corruption testing ? Can you use SQLite to see whether it is already corrupt ? Or can the test run on a brand new, freshly-created database ? If neither of those, your test won't be fair.
Corruption in databases spreads. One incorrect pointer can lead to new data being lost. An incorrect row-length can lead to changes being made to the wrong part of the file, overwriting data which shouldn't be changed. SQLite will continue to work with a corrupt database if it never notices it's corrupt. But without the above test process there's no reason for it to suddenly get paranoid about every piece of data it finds. SQLite includes a PRAGMA command which tests the database /fairly/ thoroughly looking for such problems. This is often included as part of a power-on test, or a weekly/monthly/yearly maintenance procedure. Without this test, it's possible that the SQLite database file has been corrupt for years. Or you can run it yourself any time if you can copy the database to your own computer. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
