On Wed, Jun 27, 2012 at 10:13 AM, Anthony <abasta...@gmail.com> wrote: >> Again, with autocommit off: >> The server process does a query/select to see if there is any work to >> do. This provokes SQLite to acquire a SHARED lock. Then the server >> process decides "oops, no work to do, let's go to sleep for a minute". >> Notice that it does nothing to release that lock. > > > Yes, it does release the lock, as soon as the select is complete. You do not > have to do db.commit() after a select.
Please show me where that is documented. Section 7 of http://www.sqlite.org/lockingv3.html says that ONLY happens when autocommit is on, and you have stated that it is off (contrary to my mistaken memory). Further, The Book says that only inside of a Web2py app does commit/rollback back happen automatically. Thanks, --Doug --
