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 |
Subject: | Re: Ambiguous usage of 'any' in explanation |
Date: | 2018-10-13 03:23:09 |
Message-ID: | 20181013032309.GA21857@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)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(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 +
From | Date | Subject | |
---|---|---|---|
Next Message | KES | 2018-10-13 09:25:38 | Re: Ambiguous usage of 'any' in explanation |
Previous Message | David G. Johnston | 2018-10-12 21:37:33 | Re: Ambiguous usage of 'any' in explanation |