Re: Ambiguous usage of 'any' in explanation

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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-10-15 06:00:18
Message-ID: CAKFQuwbbuCS3wtp49uQF7y_-zEbsg12KokzGWEQ2ui5hSC9Ekw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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.

David J.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2018-10-15 16:32:20 Re: Ambiguous usage of 'any' in explanation
Previous Message Thomas Munro 2018-10-14 21:47:27 Re: bloom documentation patch