> What about the I of ACID? The select should have an implicit transaction > around it.
No, it shouldn't. It can be a part of some other transaction. I in ACID means Isolation of transactions, not Isolation of select statements. Otherwise there would be no way for select statement to read uncommitted data in the same transaction. Pavel On Wed, Jun 1, 2011 at 2:57 PM, Robert Myers <rob.my...@ziften.com> wrote: > On 6/1/2011 1:47 PM, Pavel Ivanov wrote: >>> Actually, you do know what SQLite does without knowing the internals. It >>> claims to be serializable and ACID >>> (http://www.sqlite.org/transactional.html), therefore it's fine. >> "Serializable" there means that once transaction is started statements >> won't see any data committed in other transactions. But it doesn't >> impose any restrictions on how statements should behave within the >> same transaction. And in SQLite it's pretty unpredictable and so even >> SQLite's documentation prohibits updating some table while select >> statement on it is active (I can find a link on sqlite.org for you >> when I have some spare time). > What about the I of ACID? The select should have an implicit transaction > around it. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
