[sqlite] BUSY on COMMIT when EXCLUSIVE is held is an unexpected result

I have this case: Thread 1 Thread 2 -- BEGIN EXCLUSIVE BEGIN EXCLUSIVE - BUSY ... etc ... BEGIN EXCLUSIVE - BUSY COMMIT BEGIN EXCLUSIVE - OK ... The

Re: [sqlite] BUSY on COMMIT when EXCLUSIVE is held is an unexpected result

On 12/17/2010 07:54 PM, Ben Harper wrote: I have this case: Thread 1 Thread 2 -- BEGIN EXCLUSIVE BEGIN EXCLUSIVE - BUSY ... etc ... BEGIN EXCLUSIVE - BUSY COMMIT

Re: [sqlite] BUSY on COMMIT when EXCLUSIVE is held is an unexpected result

I'm using rollback - and no it's nothing like trying to commit inside a user-defined function. Very simple usage pattern. I'll isolate the code so that it's small enough to post here. I just noticed that I do sqlite3_busy_timeout(DB,0) - if that's relevant. Ben -Original Message- From: