From: sad <sad@bankir.ru>
To: Richard Huxton <dev@archonet.com>
Cc: Rosser Schwarz <rosser.schwarz@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: feature request ?
Date: Fri, 25 Jun 2004 11:54:05 +0400
Message-ID: <200406251154.05331.sad@bankir.ru> (raw)
In-Reply-To: <40DBE35A.70104@archonet.com>
References: <200406250816.47781.sad@bankir.ru>
<200406251020.41387.sad@bankir.ru>
<40DBE35A.70104@archonet.com>
> sad wrote:
> > On Friday 25 June 2004 09:37, Rosser Schwarz wrote:
> >>On Fri, 25 Jun 2004 08:16:47 +0400, sad <sad@bankir.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 !!!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sad@bankir.ru, dev@archonet.com, rosser.schwarz@gmail.com
Subject: Re: feature request ?
In-Reply-To: <200406251154.05331.sad@bankir.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox