Re: So what's null then if it's not nothing?
From: Frank Hamersley <terabitemightbe_at_bigpond.com>
Date: Fri, 25 Nov 2005 03:27:55 GMT
Message-ID: <%wvhf.3314$ea6.2753_at_news-server.bigpond.net.au>
[..]
>
> Sorry - no. Not enough said by a long chalk. Everything stored on a
> database is a known fact. What does datum/data actually mean? It is
> ridiculous to store the "fact" that we don't know something. Only
> inadequacies in a model can come anywhere near accounting for a need to
> do this.
Date: Fri, 25 Nov 2005 03:27:55 GMT
Message-ID: <%wvhf.3314$ea6.2753_at_news-server.bigpond.net.au>
michael_at_preece.net wrote:
> FrankHamersley wrote:
>>michael_at_preece.net wrote: >>>Hugo Kornelis wrote: >>>>On Wed, 23 Nov 2005 01:09:56 GMT, Frank Hamersley wrote: >>>>>Hugo Kornelis wrote:
[..]
>>> >>>Omitting the row sounds right. Using NULL is certainly wrong. The thing >>>doesn't exist. Nor does <WhatYouDidLastNight/>. Using NULL for >>>everything that doesn't exist would take up a considerable amount of >>>storage space - like the size of the known universe and more. >> >>Everything after the 1st sentence of the preceding para itself is worthy >>of NULL. Nuff said!
>
> Sorry - no. Not enough said by a long chalk. Everything stored on a
> database is a known fact. What does datum/data actually mean? It is
> ridiculous to store the "fact" that we don't know something. Only
> inadequacies in a model can come anywhere near accounting for a need to
> do this.
Why is that? </OT>
Cheers, Frank. Received on Fri Nov 25 2005 - 04:27:55 CET