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: <c3hpn19ne9ghnjdpsvkka0hk3df8u518j9_at_4ax.com>


On Thu, 17 Nov 2005 17:00:23 +0100, Alexandr Savinov <spam_at_conceptoriented.com> wrote:

[snip]

>> An RDBMS as a set of know facts. If I have dogs with
>> and without colour then I have at least two relvars one with and one
>> without a colour attribute. If I need to distinguish between colourless
>> dogs and dogs of which I don't know the colour then I add an attribute
>> to indicate that fact. I don't need to add a null.
>
>Sometimes you need. For example, if you are not allowed to create more
>tables. Such design can be more or less attractive but nothing changes

     Why do you use such an inflexible system?

[snip]

Sincerely,

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

Original text of this message