Hi Tom,
Whilst not knowing much about the process, I have a recollection about something in the documentation that said if sqlite thought that there was a potential for deadlock the busy handler was never even called. Could that explain this ? Cheers Owen -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Tom Broadbent Sent: Friday, November 20, 2009 7:27 PM To: sqlite-users@sqlite.org Subject: [sqlite] begin transaction i have several processes all trying to write to a given DB. i have set sqlite3_busy_timeout to 10000 (10 sec). when proc A successfully beings a trasaction IMMEDIATE what appears to happen when proc B attempts to begin transaction IMMEDIATE is that it fails immediately w/ SQLITE_BUSY. i would expect that proc B would wait 10 sec trying to begin transaction rather than fail immediately. is this expected? thanks tom ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ 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
