| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adam Mackler <adam(at)mackler(dot)email> |
| Cc: | postgresql(at)mackler(dot)email, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: unclear syntax explanation for multiple window definitions in a SELECT query |
| Date: | 2023-02-17 17:09:34 |
| Message-ID: | CAKFQuwYx9wD59YjJ+OYf7JQ5WP7eN1FP9ktdGYBNk-QXFvDhnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Feb 16, 2023 at 10:18 AM Adam Mackler <adam(at)mackler(dot)email> wrote:
>
> Maybe the reference section for SELECT is the wrong place for that longer
> form, but section 4.2.8 (or some other referenced from there) could be.
>
>
Expanding Section 7.2.5 to be more consistent in level-of-detail with the
rest of that page (syntax and examples in particular) seems like an easy
sell.
https://www.postgresql.org/docs/current/queries-table-expressions.html#QUERIES-WINDOW
I'm not convinced that modifying the SELECT page to make all of the
relevant [, ...] items [, blah-blah-blah ] instead is going to be a net
improvement.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-02-19 03:10:43 | Transaction wraparound and read committed isolation level |
| Previous Message | Adam Mackler | 2023-02-16 17:18:41 | Re: unclear syntax explanation for multiple window definitions in a SELECT query |