Re: [sqlite] sqlite3_open on non-DB files / corrupt DBs - Found word(s) list error in the Text body

On 25 Nov 2010, at 5:25pm, Tito Ciuro wrote: > 1) SELECT on sqlite_master. All SQLite3 databases contain it, so it would > fail right away is it wasn't a valid database. > 2) Issue a "PRAGMA integrity_check" statement, if (1) succeeds. > > However, I'm wondering whether (1) is redundant. If

Re: [sqlite] sqlite3_open on non-DB files / corrupt DBs - Found word(s) list error in the Text body

Hi Nick, On Nov 25, 2010, at 2:09 PM, Nick Shaw wrote: > 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

Re: [sqlite] sqlite3_open on non-DB files / corrupt DBs - Found word(s) list error in the Text body

Tito Ciuro wrote: > On 25 Nov 2010, at 12:51, Igor Tandetnik 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