Richard Klein wrote:
John Firebaugh wrote:
I take it this mean that if, say, thread A begins a transaction, and
modifies the database, then thread B modifies the database, then thread
A commits the transactions, B's modifications are also committed?
Nope. Once thread A begins a transaction, no other thread (or process)
can modify the database until thread A commits. (That's what "atomic
transaction" means!)
In the above scenario, thread B will likely get a SQLITE_BUSY when he
tries to UPDATE. He should sleep for awhile and try again.
- Richard Klein
Oops, didn't read the fine print: Threads A and B share a connection.
I don't know what would happen in that case.
- Richard
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
