On Wed, 2005-03-16 at 22:40 +0100, Jakub Adamek wrote:
> Also the error description "database TABLE is locked" is sometimes wrong
> because it is the whole database which is locked. Perhaps another error
> code/message should be created for "database is locked" (e.g. with open
> cursors).
>
There are two different errors:
SQLITE_BUSY - another process has the whole database locked
SQLITE_LOCKED - one sqlite3_step() is trying to read (or write)
the same table that another sqlite3_step() is
writing (or reading) using the same DB handle.
It sounds as if Mr. Strittmatter is getting the second error.
The cause of SQLITE_LOCKED is usually because you failed to
sqlite3_finalize() the previous statement.
--
D. Richard Hipp <[EMAIL PROTECTED]>
