Home -> Usenet -> comp.databases.theory -> Re: So what's null then if it's not nothing?

Re: So what's null then if it's not nothing?

From: FrankHamersley <FrankHamersleyZat_at_hotmail.com>
Date: Wed, 23 Nov 2005 10:59:48 GMT
Message-ID: <EYXgf.1705$ea6.525_at_news-server.bigpond.net.au> 






mountain man wrote:


> "paul c" <toledobythesea_at_oohay.ac> wrote in message 


> news:CIQgf.578722$tl2.426979_at_pd7tw3no...



>>mountain man wrote:
>>>"paul c" <toledobythesea_at_oohay.ac> wrote in message 
>>>>Frank Hamersley wrote:
>>>>>JOG wrote:
>>>>>>michael_at_preece.net wrote:




[..]


> 

> The technical implementation of the handling of null values


> within the different RDBMS and DBMS software vendors

> such as Microsoft, Oracle, IBM, etc are diverse, as are

> the various kinds of breakfast cereals.




Do you know of a reference that explains these variations succinctly - I 
must admit my breadth of vendor quotient is quite low.



Until now I had assumed most (if not all) performed the 3VL fandango in 
the same direction around the dance floor - especially the (NULL == 
NULL) is FALSE outcome.



I had (previously?) thought the angst in this issue was more driven by 
ppl being aggravated by the "apparently" non-sensical outcomes when NULL 
values appear in join elements and/or procedural code and lead to 
unexpected results (bugs).



Cheers, Frank. (Germany 06 Oi Oi Oi)
Received on Wed Nov 23 2005 - 11:59:48 CET












Original text of this message