On 12 Jan 2011, at 10:54pm, Max Vlasov wrote: > On Thu, Jan 13, 2011 at 1:07 AM, Simon Slavin <slav...@bigfraud.org> wrote: > >> [snip] If you're just >> letting your user change whatever data they want, why are you bothering to >> keep track of rowids ? >> >> > Thanks to the portability of sqlite, sometimes I just want to do things easy > at the fingers. So you have a grid, you walk on it, change values, sometimes > the program says "sorry, you can not do this", in other cases it just does > what it was asked for. And for for maintaining such simplicity one sometimes > have to implement a tricky algorithm like this :)
I didn't make my question clear. Why are you keeping track of rowids through changes. Since a change to any one record can make changes to any number of records in any number of trees you have to redraw the screen after every change anyway. So why are you bothering to keep track of the rowid of just one of the records which were changed ? As you redraw the display you can work out the new rowids. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
