Re: NULLS and User Input WAS Re: multimaster

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: NULLS and User Input WAS Re: multimaster
Date: 2007-06-04 14:08:23
Message-ID: 20070604140823.GL32320@phlogiston.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 04, 2007 at 12:37:42AM +0200, PFC wrote:
> NULL usually means "unknown" or "not applicable"

Aaaargh! No, it doesn't. It means NULL. Nothing else.

If it meant unknown or not applicable or anything else, then

SELECT * FROM nulltbl a, othernulltbl b
WHERE a.nullcol = b.nullcol

would return rows where a.nullcol contained NULL and b.nullcol
contained NULL. But it doesn't, because !(NULL = NULL).

It's too bad indeed that the originators of SQL used three-value
rather than five-value logic, but this is what we have. If you
happen to want to use NULL to mean something specific in some
context, go ahead, but you shouldn't generalise that to "usually
means" anything.

A

--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
Everything that happens in the world happens at some place.
--Jane Jacobs

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Franz.Rasper 2007-06-04 14:16:14 Re: Corruption of files in PostgreSQL
Previous Message Magnus Hagander 2007-06-04 13:40:27 Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2