>> So executing the insert/update/delete statement places RESERVED lock >> right from the start before executing nested selects? > > Yes.
Then I stand corrected. Thank you. Pavel On Tue, Aug 18, 2009 at 2:04 PM, Dan Kennedy<[email protected]> wrote: > > On Aug 19, 2009, at 1:01 AM, Pavel Ivanov wrote: > >>> Cannot happen. If not executed within an implicit transaction, each >>> SQL statement is effectively wrapped in a transaction all of its own. >> >> So executing the insert/update/delete statement places RESERVED lock >> right from the start before executing nested selects? > > Yes. > > Dan. > > _______________________________________________ > 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
