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
{{ message }}
Repository navigation
Commit 7dcdeec
Browse filesBrowse the repository at this point in the historyBrowse files
DuckDB: support QUALIFY after WINDOW, OVER (w ...) and FILTER without WHERE (#2803)
* DuckDB: support QUALIFY after WINDOW, OVER (w ...) and FILTER without WHERE
- QUALIFY may follow the WINDOW clause and prints back there
(`PlainSelect.isQualifyAfterWindow()`).
- A window specification may start with the name of the window it
extends, `OVER (w ORDER BY b)`, also in WINDOW definitions
(`WindowDefinition.getBaseWindowName()`).
- `FILTER (b > 1)` without WHERE is accepted except under the
PostgreSQL dialect (`AnalyticExpression.isFilterWhereKeyword()`).
* Keep window specifications parseable inside lookahead
- The base window name is a choice rather than an optional, so that
lookahead scans through a window specification keep its check:
`JSON_VALUE(... DEFAULT sum(a) OVER (PARTITION BY b) ON EMPTY)` parses
again.
- Only an OVER window may extend a named window, not WITHIN GROUP.
- QUALIFY after WINDOW requires a WINDOW clause.
0 commit comments