Tito Ciuro wrote: > On 25 Nov 2010, at 12:51, Igor Tandetnik <itandet...@mvps.org> wrote: > > Run "PRAGMA integrity_check" right after opening. > > That could be a potentially slow operation if the database is valid and contains lots of records. > Wouldn't be better to issue a SELECT statement and let SQLite come back with a SQLITE_NOTADB error right away?
As Igor points out, that may not fail if the corruption is in a table you don't query. In this case, the databases I'm working with are either small enough for the speed of an integrity check not to be an issue, or the integrity of the database is more important than a delayed DB open (which happens in a seprate thread to my apps' main GUI, so the user won't notice an issue anyway). Thanks for all the help peeps, Nick. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
