On Thu, Feb 16, 2023 at 10:18 AM Adam Mackler 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 p
Section 4.2.8 does have
a single mention of existing_window_name in bold italics, as if it would be
described in more detail lower on the page, but that's the only mention of it
there.
The only instruction for how to have multiple window definitions is then in the
SELECT reference, where it is repre
ar in
> explaining how to use multiple window definitions. It's easy to read it
> and
> believe that multiple WINDOW keywords, one for each definition, are
> correct,
> which is not the case.
>
> See this stackoverflow question and answer on point:
>
> https://s
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/sql-select.html
Description:
The syntax documentation for SELECT in SQL COMMANDS section is unclear in
explaining how to use multiple window definitions. It's easy to read it and
be
PG Doc comments form writes:
> According to the spec:
> [ WINDOW window_name AS ( window_definition ) [, ...] ]
> So the ... means I can have more than one named window. But I can't make
> this work on 11.5.
It's supposed to be WINDOW w1 AS (...), w2 AS (...), ...
ie don't repeat the WINDOW keywo
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-select.html
Description:
According to the spec:
[ WINDOW window_name AS ( window_definition ) [, ...] ]
So the ... means I can have more than one named window. But I can't make
this
