Re: [sqlite] SQLITE_BUSY on rare occasions, single thread, single connection

Thank you all very much for your answers.. On Mon, Jul 22, 2013 at 9:07 AM, RSmith wrote: > - You have another open operation or transaction which has not been > committed or finalized or in some way completed. If I only have one connection, there can't be another uncommitted transaction? > Bo

[sqlite] SQLITE_BUSY on rare occasions, single thread, single connection

Hey everybody. I'm getting SQLITE_BUSY on sqlite_step on insert statement, that is part of an explicit transaction of multiple statements. There is only 1 thread and 1 connection, so there should not be anything holding a lock. It does not happen very often, so I'm having a hard time debugging it.