If they are both using the same connection, yes. Transaction state is an attribute of the connection, not the statement or thread.
--- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of pisymbol . >Sent: Thursday, 28 September, 2017 13:02 >To: SQLite mailing list >Subject: Re: [sqlite] FULLMUTEX and exclusive transactions between >threads > >On Thu, Sep 28, 2017 at 2:10 PM, Simon Slavin <slav...@bigfraud.org> >wrote: > >> >> >> On 28 Sep 2017, at 6:57pm, Keith Medcalf <kmedc...@dessus.com> >wrote: >> >> > The mutex is used to prevent multiple concurrent entry (ie, >calling an >> sqlite3_* function) using the same connection from multiple >threads. (ie, >> serialization). It does not provide isolation of any sort. THat is >to say >> that you can prepare a statement on a connection and then step it >on >> another and finzalize on a third. What you cannot do (and what >> serialization prevents) is have two threads make calls at the same >time on >> the same connection object. >> > >So you can still have issues with thread 1 issuing a "BEGIN" and then >thread 2 issuing another "BEGIN" before thread 1 finalizes the >transaction >causing failure. Correct? > >-aps >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
