Hmm really?

Odd thing is that although I do have a 10 second timeout as soon as C goes
into a begin transaction A receives the SQLITE_BUSY error, in other words I
don't see any 10 second delay.

I'll try increasing the timeout.



-----Original Message-----
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin
Sent: October-29-13 8:48 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Problem with SQLITE_BUSY


On 29 Oct 2013, at 10:26pm, Normand Mongeau <nmong...@theobjects.com> wrote:

> I have a situation where I always run into an SQLITE_BUSY error. 

Set your timeout to something very large (a million milliseconds ?) and see
if the problem just turns into unexpected delays instead of errors.  You can
set timeout using either of these:

easy:

http://www.sqlite.org/pragma.html#pragma_busy_timeout

difficult:

http://www.sqlite.org/c3ref/busy_timeout.html

Simon.
_______________________________________________
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

Reply via email to