Have you committed the transaction on connection1?
--- () ascii ribbon campaign against html e-mail /\ www.asciiribbon.org > -----Original Message----- > From: [email protected] [mailto:sqlite-users- > [email protected]] On Behalf Of J Decker > Sent: Wednesday, 19 June, 2013 14:59 > To: General Discussion of SQLite Database > Subject: [sqlite] Deadlock with multiple connections > > I have a sqlite database that ends up with 3 connections from the same > program in a single thread. The first, only SELECT statements are > used. The second, is opened, a BEGIN TRANSACTION issued and then some > inserts. I end up opening a 3rd connection to the database and issue > another begin transaction and start more inserts. > > 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. > > COMMIT - busy > insert - busy > commit - busy > insert - busy > > The 3rd connection's insert is into a table that has been inserted > into by the 2nd connection. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
