Using busy_timeout in itself won't do the job. From what I'm gathering I need to rollback the transaction that returned BUSY, reset the statement and retry once the database is not BUSY anymore?I probably also don't want the default BEGIN. I probably want either IMMEDIATE or EXCLUSIVE. Additionally I also probably want logic to distinguish between deadlock BUSY and "regular" BUSY, unless IMMEDIATE/ EXCLUSIVE guarantee against a dead-lock.
On May 22, 2009, at 2:19 PM, Steven Fisher wrote: > http://www.sqlite.org/c3ref/busy_timeout.html _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
