Re: Ambiguous usage of 'any' in explanation

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@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.
> 
> I am thinking of applying my earlier patch and calling it done.

Applied and backpatched to 9.3.

-- 
  Bruce Momjian  <bruce@momjian.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 +