From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John Lumby <johnlumby(at)hotmail(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Set-Returning functions in a select list |
Date: | 2021-07-27 17:24:03 |
Message-ID: | 351778.1627406643@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
John Lumby <johnlumby(at)hotmail(dot)com> writes:
> I feel that more on this topic needs to be added to the reference information for SELECT,
> both in the description of the (expressions in the) SELECT-list and in the description of the FROM list, and in particular a note on how and why certain usages are equivalent when written in specific ways, (and maybe even which is preferred).
> Currently there is a thorough description of the semantics of [ LATERAL ] ROWS FROM in the FROM list, but very little about the effect of placing one or more what set-returning functions in the SELECT-list. Also there should be a reference to the chapters under "Query Language (SQL) Functions" , especially sub-chapter "SQL Functions Returning Sets"
The bigger picture here is that there's a lot of detail in 38.5 that
is of interest to users of built-in functions, not only to people
writing new functions. We've had discussions before about refactoring
that material so that some of it could be moved into a more prominent
place, probably in chapter 7 (Queries) or maybe chapter 9 (Functions
and Operators). Nobody's produced a coherent proposal though. In the
meantime I'm not much on board with sprinkling cross-references into
random places, if only because those references will be pointing to
the wrong place when/if this refactoring does happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2021-07-28 03:48:04 | Common case not at all clear |
Previous Message | John Lumby | 2021-07-27 16:19:42 | Set-Returning functions in a select list |