From: | sad <sad(at)bankir(dot)ru> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Rosser Schwarz <rosser(dot)schwarz(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: feature request ? |
Date: | 2004-06-25 07:54:05 |
Message-ID: | 200406251154.05331.sad@bankir.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> sad wrote:
> > On Friday 25 June 2004 09:37, Rosser Schwarz wrote:
> >>On Fri, 25 Jun 2004 08:16:47 +0400, sad <sad(at)bankir(dot)ru> wrote:
> >>>>Very simply, a boolean may have to values: true or false. It's also
> >>>>possible that it's not been set to anything (NULL).
> >>>
> >>>really ?
> >>>what about (13 < NULL)::BOOL
> >>
> >>Per the semantics of NULL, 13 is neither greater than nor less than
> >>NULL. NULL is the *unknown* value; it's impossible to meaningfully
> >>compare it to anything else. Try (NULL = NULL)::boolean. It's NULL,
> >>also.
> >
> > READ THE THREAD BEFORE ANSWER
>
> WHAT MAKES YOU THINK HE HASN'T?
I had answered to the proposal to PROHIBIT NULL VALUES
> The key point of argument, and where the problem is with your (13 <
> NULL)::BOOL point is this:
IT IS NOT MY PROBLEM !!! it is an EXAMPLE WHY WE CAN NOT PROHIBIT NULLS !!!
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2004-06-25 08:33:30 | Re: feature request ? |
Previous Message | Jan Norman Pedersen | 2004-06-25 07:16:58 | Re: rules |