You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The note about WindowFrameBound::Following being only valid "in
WindowFrame::end_bound" was both
- confusing, as it was based on the ANSI SQL syntax the parser doesn't
adhere to -- though it sounded like a promise about the AST one could
expect to get from the parser
- and incomplete, as the reality is that the bounds validation the SQL
engine might want to perform is more complex. For example Postgres
documentation says <https://www.postgresql.org/docs/11/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS>:
> Restrictions are that frame_start cannot be UNBOUNDED FOLLOWING,
> frame_end cannot be UNBOUNDED PRECEDING, and the frame_end choice
> cannot appear earlier in the above list of frame_start and frame_end
> options than the frame_start choice does — for example RANGE BETWEEN
> CURRENT ROW AND offset PRECEDING is not allowed. But, for example,
> ROWS BETWEEN 7 PRECEDING AND 8 PRECEDING is allowed, even though it
> would never select any rows.
0 commit comments