> > > Then why do you keep hammering on the idea that SQLite is somehow > incorrect or wrong? > > You've explained what you're trying to do. We've explained there is > a better way to do that, that also happens to provide the correct > answer on all platforms, AND likely runs faster-- especially if any > of those columns has an index on them. >
I gave a simple example. I work with generic cases. My application doesn't have all static SQL. A lot is from the user or built dynamically. > > > What if the SET and WHERE contain many columns? > > Then you're asking for a more complex operation. Your SQL gets a bit > more complex as well. > > > Now I have to add a "WHERE column<>mynewval" for every column in SET > > to get the actual changes, something like UPDATE testtable SET col1=?1, > > col2=?2, col3=? WHERE <insert> complex where clause > > AND col1<>?1 AND col2<>?2 AND col3<>?3. > > > (passing a null parameter to the above won't even work!) > > Well, no, it won't, because you're using the wrong operator. > > Use "WHERE col1 IS NOT ?1 AND..." and it all works fine. > > OK thanks, so I should always use IS NOT where I always used <>. Oh well (talk about yuck!) > > No surprises there. Oracle has never managed to impress me. > > I know what you mean. That MySQL database they make is difficult to > take seriously. > > Very funny. They didn't make it, they own it now. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
