John Stanton <[EMAIL PROTECTED]> wrote:
Igor, I confused the issue with names. The correct name is a
"reserved" lock, created when a simple transaction is launched in
"deferred"
mode. Here is the Sqlite explanation.
A BEGIN IMMEDIATE or EXCLUSIVE will acquire a write lock immediately.
Yes. And that may fail with SQLITE_BUSY. But once it succeeds,
subsequent SELECT statements will always succeed, too.
How does your observation help prove the point that every single
sqlite3_step call may return SQLITE_BUSY? This is the only claim of
yours I'm arguing against.
Igor Tandetnik
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
