Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Marcus Grimm
> On Tue, 27 Oct 2009 21:50:12 +0100, "Marcus Grimm" > wrote: > >>PS: Does anybody know how I can edit this >>example code ? I recently attempted to add a clear >>PD statement and also add some comments but when >>I try to edit I allways end up in the wiki index page... >

Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Kees Nuyt
On Tue, 27 Oct 2009 21:50:12 +0100, "Marcus Grimm" wrote: >PS: Does anybody know how I can edit this >example code ? I recently attempted to add a clear >PD statement and also add some comments but when >I try to edit I allways end up in the wiki index page... Last time

Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Marcus Grimm
> Thanks! I ran the example code and it seems like every UPDATE fails > with errors like the following: > > SqlStep Timeout on handle: 8 (rc = 6) > SqlStep tries on handle 8: 200 > BeginTrans Timeout/Error on handle: 8, Errorcode = 6 > Write Thread: DB is busy! tries = 142 handle = 8 > > Looking

Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Pavel Ivanov
> Are these errors normal? If you're executing select statement, never get all rows from it and never reset/finalize it then yes, all updates from other thread will fail and it's normal. Pavel On Tue, Oct 27, 2009 at 1:42 PM, Chris T wrote: > Thanks!  I ran the example

Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Chris T
Thanks! I ran the example code and it seems like every UPDATE fails with errors like the following: SqlStep Timeout on handle: 8 (rc = 6) SqlStep tries on handle 8: 200 BeginTrans Timeout/Error on handle: 8, Errorcode = 6 Write Thread: DB is busy! tries = 142 handle = 8 Looking at the database

Re: [sqlite] Deadlock with two local instances

2009-10-27 Thread Marcus Grimm
> Another odd thing is that when I call sqlite3_reset on the prepared > statement, it also returns SQLITE_BUSY. Should I only reset the > statement when it has been executed successfully? one possible approach when getting SQLITE_BUSY is to retry the sqlite3_step call until it finally gets thru.

Re: [sqlite] Deadlock with two local instances

2009-10-26 Thread Chris T
Another odd thing is that when I call sqlite3_reset on the prepared statement, it also returns SQLITE_BUSY. Should I only reset the statement when it has been executed successfully? On Mon, Oct 26, 2009 at 2:40 PM, Chris T wrote: > I'm new to sqlite (and sql in general,