sorry, don't have a simple explanation...some implementations of the original theory are a bit off based on DB vendor, but I will do a bit of research and get back to you... -----Original Message----- From: Sterin, Ilya [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 6:06 PM To: 'Mitsuda, Alex '; '[EMAIL PROTECTED] ' Subject: RE: = NULL vs. IS NULL
Then explain assigning NULL to values in the update query and not being able to query based on NULL as for foo=NULL, but set foo=NULL is legal. Ilya -----Original Message----- From: Mitsuda, Alex To: [EMAIL PROTECTED] Sent: 10/23/01 4:03 PM Subject: RE: = NULL vs. IS NULL ...choosing to disagree in this case is like saying you would prefer to find oak leaves on a maple tree, unfortunately. The definition of NULL in relational databases was defined by Codd & Date when they defined the theory of relational databases and the sets of data that are valid. -----Original Message----- From: Bart Lateur [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 5:57 PM To: [EMAIL PROTECTED] Subject: Re: = NULL vs. IS NULL On Tue, 23 Oct 2001 12:35:57 -0500, Stephen Clouse wrote: >This is not Oracle, but ANSI-standard behavior. NULL represents the absence or >non-existence of a value. A non-existent value cannot be equal to anything. So >this is the correct behavior. I personally don't think DBI should muck with >proper behavior. My personal opinion is to disagree. To me, NULL means "empty". It is not the same as a zero length string. But empty is empty, thus NULL=NULL. Nitpicking that NULL != NULL, is only making our life harder. Last week, there was a similar discussion going on, on the Perl6 mailing lists, with regards to NaN (Not A Number). Is NaN==Nan, or NaN!=NaN? -- Bart. ******************************************************** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. All e-mails at Neuberger Berman are, in accordance with Firm policy, to be used for Neuberger Berman business purposes only. E-mails sent from or to the Firm are subject to being reviewed by the Firm in accordance with the Firm's procedure for the review of correspondence. ******************************************************** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. All e-mails at Neuberger Berman are, in accordance with Firm policy, to be used for Neuberger Berman business purposes only. E-mails sent from or to the Firm are subject to being reviewed by the Firm in accordance with the Firm's procedure for the review of correspondence.
