| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(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 14:20:21 |
| Message-ID: | 17406.1541168421@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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."
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-11-02 17:05:38 | Re: pgsql: doc: use simpler language for NULL return from ANY/ALL |
| Previous Message | Bruce Momjian | 2018-11-02 13:11:16 | pgsql: GUC: adjust effective_cache_size docs and SQL description |