Yes, they are perfectly valid. The only thing that can bite you is if you are in process of fetching rows from some select statement and you update row that was just fetched or update/insert rows that would have been fetched later by the select statement. This is generally a bad thing to do and behavior of SQLite in such case is undefined.
Pavel On Fri, Feb 12, 2010 at 12:09 PM, dv74 <d...@esko.com> wrote: > > I need a confirmation that these operations (i.e reading back the rows, that > were just modified/inserted while the transaction is occuring) are valid and > will not bite me in the long run. > > > > Pavel Ivanov-2 wrote: >> >> Besides the fact that I don't understand what you have meant by these >> lines: >> >>> Select * from table where lookup_key = "ABC" >>> append save results to my list. >> >> I don't see anything unusual in your algorithm. What do you want us to >> verify (which you cannot verify yourself) and what do you find unusual >> in your actions? >> >> Pavel >> > > -- > View this message in context: > http://old.nabble.com/Nesting-Read-Write-within-Transaction--tp27565519p27566601.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > 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
