I've been using the IS operator to the exclusion of = in my application's queries so that I'm not surprised by some input being null and giving unexpected results. My rationale is that if I'm consistent, my software will be as well (all else being equal, anyway...).

The IS operator is commonly seen in tutorials and the like as "x IS NOT NULL", and Richard's example earlier today of the unary NOT operator "a = NOT b" started me wondering if there are any performance or portability concerns with using IS rather than =. Are there any other reasons I might perhaps want to use = rather than IS that I'm not aware of?


Thanks. :)

--
J. King

_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to