Simon, As per my understanding I am getting the result set and trying to change values in the table based on what I read from the result set up to that point. I see no reason why I should be stopped from updating the row I have already read in the result set.
Simon Slavin-3 wrote: > > > On 7 Nov 2010, at 6:14pm, cricketfan wrote: > I don't understand why you find this surprising. You have two pieces of > program: one is trying to look at something while the other is in the > middle of changing it. They are going to argue about which one can access > those values. > > You can complete the scan first, then make the changes you want. Or if > the changes depend on the scan, use an UPDATE ... WHERE command that does > all the work for you. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://old.nabble.com/sqlite3_step-to-select-and-update-the-same-table-tp30152284p30157400.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
