> This is interesting. I often have situations where I SELECT something > and then do manipulations (INSERT/DELETE/UPDATE) on the db as I > iterate through the results. > > Is this what you mean by your statement? If yes, how should such > situations be avoided, and why?
If you issue BEGIN statement before you do your SELECT then yes, that's what I'm talking about (and I said how to avoid it - issue BEGIN IMMEDIATE instead of BEGIN). If you don't issue BEGIN then your SELECT and UPDATE are executed in different transactions (are you aware of some races that can happen that way?), so my statement is not applicable. Pavel On Mon, Jun 14, 2010 at 8:44 AM, Robert Latest <boblat...@googlemail.com> wrote: > On Fri, Jun 11, 2010 at 5:26 PM, Pavel Ivanov <paiva...@gmail.com> wrote: > >> 1. Ensure that you have no transactions started with SELECT and >> continued with INSERT/DELETE/UPDATE > > This is interesting. I often have situations where I SELECT something > and then do manipulations (INSERT/DELETE/UPDATE) on the db as I > iterate through the results. > > Is this what you mean by your statement? If yes, how should such > situations be avoided, and why? > > Regards, > robert > _______________________________________________ > 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
