>> A connection holds a SHARED lock. It did start a DEFERRED transaction then >> read something. Now it executes COMMIT.
>You are one of the rollback journaling modes, not WAL mode, right? >Different rules apply for WAL mode. > >In rollback mode, the connection automatically promotes to EXCLUSIVE >while committing the transaction. This is necessary to make sure no >other connections are simultaneously reading the database, because it >would not work for the committer to change content out from under the >other readers. After the COMMIT, it falls back to unlocked. >-- >D. Richard Hipp >d...@sqlite.org I'm pretty sure you missed the bit where he said that there was only a read, and no changes were made or requested. Otherwise, as Igor said, there's be deadlocks with any concurrent access. (Or my brain is broken on a Friday, which has been known to happen) _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
