On Thu, 2005-06-16 at 11:25 -0700, Kevin Schmeichel wrote: > As I reported earlier, after updating to sqlite > 3.2.2, I started getting occasional SQLITE_CORRUPT > errors. The next query always worked, so the error > was only a temporary condition. I decided that if I > got an error on a query, I would retry the query after > closing and reopening the db. I tried this, but I saw > the SQLITE_CORRUPT error repeat itself. Next thought > was that maybe sqlite just needed a bit of time to > "uncorrupt" itself, so I put in a sleep of 300 ms > before retrying the failed query. Seems to work... >
There should never be such a thing as a transient SQLITE_CORRUPT error. You should only get an SQLITE_CORRUPT error if the database file is truly and permanently corrupted. -- D. Richard Hipp <[EMAIL PROTECTED]>
