| 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 |
| Subject: | Re: Ambiguous usage of 'any' in explanation |
| Date: | 2018-10-12 21:37:33 |
| Message-ID: | CAKFQuwYqEj_KaUdk83utOUJtEC6YnWio-kq1aN0=KE6ev4yhWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
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)
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-10-13 03:23:09 | Re: Ambiguous usage of 'any' in explanation |
| Previous Message | Bruce Momjian | 2018-10-12 15:04:33 | Re: Ambiguous usage of 'any' in explanation |