July 4, 2002 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/sjones/ansioptionspart2ansi_nulls.asp
July 15, 2002 at 11:26 pm
I agree with u that everyone who works with SQL Server should know how it works. I myself have told many people in my team this ANSI NULLS thing. This is simple but this is necessary to know.
Regards,
Kashif
July 16, 2002 at 6:19 am
Interesting article Steve. Kashif, I know what you're saying, but it's one of those things that I dont know WHY we have to understand. It's such a mismash of if this then that - I have to refer back to BOL anytime I care...which aint often!
Andy
July 16, 2002 at 10:25 am
Same here. I thought a short article might stick in people's minds and hopefully they won't have to research it themselves.
Thanks
Steve Jones
July 18, 2002 at 2:18 pm
I agree this is a good fact to be aware of - I didn't know of it. May save me some time one day!
I saw the title and thought this may be related to an issue one of my developers brought up.
He says that when running a select statement, records with nulls he inserts directly into the DB with CTRL 0 don't show up when he does a query, but nulls inserted through a Cold Fusion query do show up. I tried re-creating this scenario, but have been unable to. Anyone experienced this?
July 18, 2002 at 5:54 pm
Haven't seen it, but you might try posting this with another description in the T-SQL forum.
Steve Jones
April 6, 2005 at 10:13 am
Thanks for this useful article but it defies belief why anyone would write =NULL and not IS NULL.
Regards
Phil Davy
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply