From everything I've read, I would have thought this
was the case. But in practice I have been seeing
transient SQLITE_CORRUPT errors. I tried "pragma
integrity_check" and it said ok.
I'm running my app on an embedded linux machine.
The db is in ramdisk and I'm using TEMP_STORE=3, so
everything should be in ram. Since sqlite3 returns
SQLITE_CORRUPT in over 20 places, it might just be
easier to use my workaround than to try and figure out
what's happening. As I said, the error doesn't occur
that often (maybe a few times a day)...
Kevin
--- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
>
> 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]>
>
>
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
