Re: Ambiguous usage of 'any' in explanation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: KES <kes-kes(at)yandex(dot)ru>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Ambiguous usage of 'any' in explanation
Date: 2018-11-02 12:55:15
Message-ID: 20181102125515.GB4015@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, Oct 15, 2018 at 12:32:20PM -0400, Bruce Momjian wrote:
> On Sun, Oct 14, 2018 at 11:00:18PM -0700, David G. Johnston wrote:
> > On Saturday, October 13, 2018, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > On Sat, Oct 13, 2018 at 12:25:38PM +0300, KES wrote:
> > > >or NULL if any of the comparisons result in unknown
> > > result in unknown??
> >
> > Well, SQL has a three-valued logic, and UNKOWN values are treated like
> > NULL.  For me they have always been the same, and I would like to avoid
> > "unknown" in this context, if possible.
> >
> >
> >
> > I was just trying to avoid using the word null twice in the same sentence but
> > it’s not a strong aversion.
>
> I am thinking of applying my earlier patch and calling it done.

Applied and backpatched to 9.3.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2018-11-02 13:11:13 Re: effective_cache_size
Previous Message PG Doc comments form 2018-11-01 00:26:53 Tipos de datos enteros