Re: Ambiguous usage of 'any' in explanation - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Ambiguous usage of 'any' in explanation
Date
Msg-id CAKFQuwbbuCS3wtp49uQF7y_-zEbsg12KokzGWEQ2ui5hSC9Ekw@mail.gmail.com
Whole thread Raw
In response to Re: Ambiguous usage of 'any' in explanation  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Ambiguous usage of 'any' in explanation  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
On Saturday, October 13, 2018, Bruce Momjian <bruce@momjian.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.

pgsql-docs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: bloom documentation patch
Next
From: Bruce Momjian
Date:
Subject: Re: Ambiguous usage of 'any' in explanation