On Aug 25, 2010, at 11:04 PM, Pavel Ivanov wrote: >> Prior to version 3.6.5 SQLite used to delay committing the >> transaction until all SELECT statements had finished. But that >> behavior was deemed to be less intuitive. > > But this is the current 3.7.1 documentation > (http://www.sqlite.org/lockingv3.html): > > ---------------- > If multiple commands are being executed against the same SQLite > database connection at the same time, the autocommit is deferred until > the very last command completes. For example, if a SELECT statement is > being executed, the execution of the command will pause as each row of > the result is returned. During this pause other INSERT, UPDATE, or > DELETE commands can be executed against other tables in the database. > But none of these changes will commit until the original SELECT > statement finishes. > ---------------- > > Is this documentation too old?
I think so. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
