Re: Ambiguous usage of 'any' in explanation

2018-11-02 Thread Bruce Momjian
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 wrote: > > > > On Sat, Oct 13, 2018 at 12:25:38PM +0300, KES wrote: > > > >or NULL if any of the comparisons

Re: Ambiguous usage of 'any' in explanation

2018-10-15 Thread Bruce Momjian
On Sun, Oct 14, 2018 at 11:00:18PM -0700, David G. Johnston wrote: > On Saturday, October 13, 2018, Bruce Momjian 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 t

Re: Ambiguous usage of 'any' in explanation

2018-10-14 Thread David G. Johnston
On Saturday, October 13, 2018, Bruce Momjian 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 b

Re: Ambiguous usage of 'any' in explanation

2018-10-13 Thread Bruce Momjian
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

Re: Ambiguous usage of 'any' in explanation

2018-10-13 Thread KES
>or NULL if any of the comparisons result in unknownresult in unknown?? 13.10.2018, 00:37, "David G. Johnston" :On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian wrote:Sorry, but I don't like this wording.  The problem is that the comparison has two row sets --- the left-hand side, a

Re: Ambiguous usage of 'any' in explanation

2018-10-12 Thread Bruce Momjian
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 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...t

Re: Ambiguous usage of 'any' in explanation

2018-10-12 Thread David G. Johnston
On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian 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-ha

Re: Ambiguous usage of 'any' in explanation

2018-10-12 Thread Bruce Momjian
On Fri, Oct 12, 2018 at 01:42:03PM +0300, KES wrote: > -   The result is NULL if the comparison does not return true for any row, > +   The result is NULL if no comparison with a subquery row returns true, >     and it returns NULL for at least one row. > -The result of ANY is “true” if the compari

Re: Ambiguous usage of 'any' in explanation

2018-10-12 Thread KES
either it is hard to understand. I will rephrase one part to show how it is easy to understand from my side:>ALL> The result is “false” if any false result is found. The result of ALL is "false" even if *at least one*  row yield false(we can use 'some' word here, but it is not such clear as *at lea

Re: Ambiguous usage of 'any' in explanation

2018-10-12 Thread KES
-   The result is NULL if the comparison does not return true for any row,+   The result is NULL if no comparison with a subquery row returns true,    and it returns NULL for at least one row.-The result of ANY is “true” if the comparison returns true for any subquery row. The result is “false” if

Re: Ambiguous usage of 'any' in explanation

2018-10-11 Thread David G. Johnston
On Thursday, October 11, 2018, Bruce Momjian wrote: > > The result is NULL if no comparison with a subquery row returns > false, and it returns NULL for at least one row. > > I can make similar adjustments in other places, and have attached a doc > patch. Does that help? > +1 Da

Re: Ambiguous usage of 'any' in explanation

2018-10-11 Thread Bruce Momjian
On Sat, Sep 15, 2018 at 11:53:47AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/functions-subquery.html > Description: > > Hi. > > The [DOC](https://www.postgresql.org/docs/10/static/f

Ambiguous usage of 'any' in explanation

2018-09-15 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/functions-subquery.html Description: Hi. The [DOC](https://www.postgresql.org/docs/10/static/functions-subquery.html) says: The result is NULL if the comparison does not retu