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 > BEGIN EXCLUSIVE -> OK > ... > > > The commit statement of Thread 1 will sometimes fail with a BUSY error. > A simple workaround is to try the commit a couple times if you receive > a BUSY error. Having done this, I cannot get this test to fail anymore.
I'm not sure how you got this to happen. One way is to try the COMMIT from within a user-defined function executed by a write statement - but that's not terribly likely. Were you using WAL mode? Or regular rollback mode (the default)? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
