On Wed, Jan 12, 2011 at 11:35 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> If you're writing an arbitrary SQL utility, I think the answer depends on > why you want to keep track of a particular record. You either want to > refresh the display or you don't, and either way the connection between old > and new rowids doesn't matter because you're going to have to redraw more > than one record. > > It's about the utility, when the data is presented with a grid and every cell of opened db and * fields of table can be edited.. I'm aware that my own actions can lead to constraint failure, but even for a legitimate change I currently can not point to the same record, and even if I could (data in this case is simply cached) I would not do this next time since this record after this change have another .rowid and it's not possible to format new "update where rowid=" query correctly. Max _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
