[Docs] Update known issues for window functions (#17097)

* draft update to known issues

* Update known issues

Remove addressed known issues. Clarify the issue with SELECT * queries.
This commit is contained in:
Charles Smith 2024-10-08 08:47:13 -07:00 committed by GitHub
parent 152330c5a8
commit 5ed68622c3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 5 deletions

View File

@ -420,8 +420,4 @@ The number of rows considered for the `moving5` window for the `count5` column:
The following are known issues with window functions:
- Aggregates with ORDER BY specified are processed in the window: ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
This behavior differs from other databases that use the default of RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW.
In cases where the order column is unique there is no difference between RANGE / ROWS; windows with RANGE specifications are handled as ROWS.
- LEAD/LAG ignores the default value
- LAST_VALUE returns the last value of the window even when you include an ORDER BY clause
- SELECT * queries without a WHERE clause are not supported. If you want to retrieve all columns in this case, specify the column names.