Michael Knigge <[EMAIL PROTECTED]> wrote: > All, > > in a application with several threads (guess 6) we sometimes encounter a > SQLITE_CORRUPT. I'm not the author of this application and my time is > spare, but I really want to ensure that this is not an SQLite issue. > > Some hints how to debug this? Anythig I could turn on within SQLite so > we can track this down? >
Is the database really corrupt, or are you getting a spurious error? You can tell if the database is truely corrupt or not by running PRAGMA integrity_check; > And yes, every thread uses its own sqlite3* ;) > Are you really sure of this? In my experience most of these kinds of problems end up being cases of threads doing things that their programmers were not aware of. -- D. Richard Hipp <[EMAIL PROTECTED]>
