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

From: Gene Wirchenko <genew_at_ucantrade.com.NOTHERE>
Date: Thu, 17 Nov 2005 09:59:46 -0800
Message-ID: <6ugpn1llgd1tqcgkn92f32v9u5bvv73q2k_at_4ax.com>


On Thu, 17 Nov 2005 16:47:53 +0100, Alexandr Savinov <spam_at_conceptoriented.com> wrote:

>JOG schrieb:
>> Alexandr Savinov wrote:
>>
>>>What people cannot understand is that we cannot simply disable nulls. It
>>>is too simplistic point of view. It is not possible to say that we will
>>>not use nulls and that is all. Why? Because the notion of absence exists
>>>in almost any data model. We need to know if an object exists or not. If
>>>yes, then we get some value. If not then we get null.

     No, if not, we get another value.

>> "absence exists in almost any data model?" That makes no sense to my
>> ears. If you don't know something why try to type it in as a fact
>> (outside some logistical efficiency considerations)?.
>
>Because sometimes we have a slot for that and we must write some value
>into it.

      You keep harping about flexibility. Why do you not use a system that does not force you to fill in unnecessary slots?

[snip]

Sincerely,

Gene Wirchenko Received on Thu Nov 17 2005 - 18:59:46 CET

Original text of this message