Re: pgsql: doc: use simpler language for NULL return from ANY/ALL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: doc: use simpler language for NULL return from ANY/ALL
Date: 2018-11-02 17:05:38
Message-ID: 20181102170538.GA4855@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Fri, Nov 2, 2018 at 10:20:21AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > doc: use simpler language for NULL return from ANY/ALL
> > Previously the combination of "does not return" and "any row" caused
> > ambiguity.
>
> IMO this is not an improvement. It's turned something that read
> reasonably well into something that sounds like it was written by
> a not very good speaker of English. In particular, the lack of
> grammatical matching between the two parts of the sentence is now
> quite confusing:
>
> The result is NULL if no comparison with a subquery row returns true,
> and it returns NULL for at least one row.
>
> The antecedent of "it" was clear before, and is not now, at least to me.
>
> Maybe you could replace that clause with "..., and at least one comparison
> returns NULL."

Agreed, done.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2018-11-02 17:05:47 pgsql: docs: adjust simpler language for NULL return from ANY/ALL
Previous Message Tom Lane 2018-11-02 14:20:21 Re: pgsql: doc: use simpler language for NULL return from ANY/ALL