On Thu, May 24, 2012 at 9:48 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 25 May 2012, at 2:45am, Andrew Cherednik > <andrew.chered...@healthscope.com.au> wrote: > >> Tried different timeouts. The timeouts will basically make the program hang, >> but eventually the transaction will end with SQLITE_BUSY error. > > Hmm. _BUSY with a timeout of 13 seconds suggests an underlying problem > rather than just a speed problem.
Also it suggests that transaction was began as read-only (with a select statement) and then there was attempt to transform it to a writing transaction (with insert, update or delete statement) when there was another writing transaction in progress waiting for this transaction to finish. Pavel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
