Re: So what's null then if it's not nothing?
Date: Fri, 18 Nov 2005 01:32:18 +0100
Message-ID: <qo7qn15ks24iootevl4ggkarohm3merd2v_at_4ax.com>
On 17 Nov 2005 14:41:19 -0800, michael_at_preece.net wrote:
>I didn't have to respond to this. If I hadn't you would never had known
>what I thought about your post. My response would not exist. What you
>would be reading here would have no value. It would have been an empty
>string. It would also have been unknown.
Hi Mike,
I'm not sure if it will survive past all filters, but I just posted an
empty message in reply to this message. I hit the reply button, selected
>You will say that at the logical level something can exist - in that it
>is part of a set - and yet have an unknown value. You would, presumably
>- also say that it does not necessarily have a value equal to empty
>string, because it's unknown. In order to record that "fact" you (or
>the SQl engine) have/has to store some code at the physical level to
>say it's not an empty string - it's null. It's not though is it? It's
>whatever you stored to represent "unknown".
It is *REPRESENTED* by whatever was chosen to *REPRESENT* the absence of a value. Don't confuse representation by what is represented.
My first name is represented by a series of four numbers on most computers. The numbers used on an ASCII machine will differ from those on an EBCDIC machine. But that doesn't make the name any different.
-1 represented in binary 1's complement is the same value as -1 represented in binary 2's complement - even though not all bits in the representation are the same.
HOW a Null is represented is irrelevant. WHAT it represents is what matters.
Best, Hugo
-- (Remove _NO_ and _SPAM_ to get my e-mail address)Received on Fri Nov 18 2005 - 01:32:18 CET