But why is this deadlocking at all? I thought there shouldn't be a problem doing this, especially since thread B is using a transaction. Shouldn't either A or B prevent the other one from accessing the database until they are done?
On 4/7/09, D. Richard Hipp <d...@hwaci.com> wrote: > > On Apr 7, 2009, at 8:57 PM, Dave Brown wrote: > >> I do finalize it - the steps I wrote were just pseudocode, but yes >> after the >> thread-A statement executes I call finalize ( or reset if I'm going >> to use >> it again ). The problem is that thread-A *never* gets to the >> finalize/reset >> call. It's thread-A which is stuck in winSleep(). >> > > In that case, you are deadlocked. Either thread-A or thread-B is > going to need to give up and retry later. > > D. Richard Hipp > d...@hwaci.com > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
