Black, Michael (IS) wrote: > Maybe my memory is fading but this is the first time I've heard anybody say > the wrapping a BEBIN around a SELECT was needed. I'd swear it was always > said it wasn't ever needed. > > > > From the docs > > http://www.sqlite.org/lang_transaction.html
> basically, any SQL command other than > SELECT<http://www.sqlite.org/lang_select.html>) will automatically start a > transaction if one is not already in effect That's, of course, documentation bug. How can you get consistent results from SELECT without taking (at least) SHARED lock? Only difference, that UPDATE/INSERT/DELETE needs RESERVED lock (and then EXCLUSIVE lock to (auto)commit), and SELECT only needs SHARED lock. > Now you're saying SELECT always starts a transaction? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
