Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

not like? Expand / Collapse
Author
Message
Posted Wednesday, April 1, 2009 2:34 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 10, 2014 9:11 AM
Points: 1,155, Visits: 1,055
DavE E (3/24/2009)
I understand all this but why doesn't Microsoft make everyones life easier and make it work as everyone expects

i.e. NULL does equal NULL

So we can use col2 = NULL or col2 != null instead of IS NULL or IS NOT NULL.

It would lead to so many less bugs


Apart from the issue of following ANSI SQL standards, when I add a clause "WHERE col1=col2" I want to be sure that the two columns contain identical data, not just that they both happen to have been left blank, or generated by a non-matched item in an outer join.



Post #687700
Posted Friday, February 15, 2013 9:52 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 12:12 AM
Points: 1,953, Visits: 2,397
good question...
very good discussion by experties



_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Post #1420858
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse