On Tue, Jul 3, 2012 at 2:45 PM, Black, Michael (IS) <michael.bla...@ngc.com>wrote:
> What's better is that it tells you what you asked for...not what you think > you asked for...which it does. > I asked for changes :-) > > You've already been shown the correct solution...a WHERE clause... > > I've done that even before posting here, just thought it odd. > You want sqlite to do a complete record compare, including following > update triggers, on EVERY record it looks at to see if something happened > to change??? > Just the fields in the SET clause. > > Yuck... > > As compare to the WHERE clause which does exactly what you want and runs > oodles faster (in all likelihood). > > I always keep an eye on the "affected rows" to see what my statements have done (whether I used a WHERE or not). Even with a WHERE, I would prefer seeing actual changes :-) _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
