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

From Bruce Momjian
Subject Re: Ambiguous usage of 'any' in explanation
Date
Msg-id 20181013032309.GA21857@momjian.us
Whole thread Raw
In response to Re: Ambiguous usage of 'any' in explanation  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-docs
On Fri, Oct 12, 2018 at 02:37:33PM -0700, David G. Johnston wrote:
> On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian <bruce@momjian.us> wrote:
> 
>     Sorry, but I don't like this wording.  The problem is that the
>     comparison has two row sets --- the left-hand side, and the right-hand
>     side.
> 
> 
> Huh...the left hand side must be a non-set scalar or row constructor.

I meant that each row feeds a value to the left-hand side to be
evaluated.

>       Each row on the left-hand side is compared with the row set on
>     the right.  I also don't like people thinking about the result of ANY
>     since it is really <comparison> ANY that is being used.
> 
> 
> Then there is some more rewording to be done since: "The result of ANY is
> “true” if any true result is obtained." (v10; 9.22.4)
> 
> Maybe:
> 
> The result of ANY is “true” if the comparison returns true for any subquery
> row; otherwise the result is “false” (or NULL if any of the comparisons result
> in unknown)

Sure.

-- 
  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 +


pgsql-docs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Ambiguous usage of 'any' in explanation
Next
From: Bruce Momjian
Date:
Subject: Re: Ambiguous usage of 'any' in explanation