Re: NULLS and User Input WAS Re: multimaster

From: "Alexander Staubo" <alex(at)purefiction(dot)net>
To: "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: NULLS and User Input WAS Re: multimaster
Date: 2007-06-04 15:03:17
Message-ID: 88daf38c0706040803u161d9d74t20e9e1876afc767d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 6/4/07, Andrew Sullivan <ajs(at)crankycanuck(dot)ca> wrote:
> 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).

I don't disagree with the principle, but that's a specious argument.
Who says (unknown = unknown) should equal true?

Alexander.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua 2007-06-04 15:04:59 current_date / datetime stuff
Previous Message Bohdan Linda 2007-06-04 14:51:38 Re: High-availability