On 19 Jun 2013, at 9:58pm, J Decker <[email protected]> wrote:

> The insert on the 3rd connection is blocked 'SQLITE_BUSY'.
> After 1 second, a COMMIT on the 1st connection is issued, and stays
> blocked with 'SQLITE_BUSY'.
> 
> so then the program alternates retrying the last commands since busy
> is supposed to be temporary.

Please do not retry commands without user interaction.

Use a SQLite call to change the timeout of your database to however long you 
think SQLite should be retrying:

<http://www.sqlite.org/pragma.html#pragma_busy_timeout>
<http://www.sqlite.org/c3ref/busy_timeout.html>

If this timeout period is exceeded, report the fault to the user.  Do not have 
your software retry.

Simon.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to