Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Umbrella development task: MDEV-6115
Other related tasks:
MDEV-9746 - CUME_DIST
Window functions in PostgreSQL 9.6: https://www.postgresql.org/docs/9.6/static/functions-window.html
Attachments
Issue Links
- relates to
-
MDEV-9922 Assertion `!join->only_const_tables() && fsort' failed in int create_sort_index
-
- Closed
-
-
MDEV-9923 ORDER BY position in window function causes strange error code
-
- Closed
-
-
MDEV-9924 Assertion `((select_options & (1ULL << 17)) ? 1 : 0)' failed in bool JOIN::make_aggr_tables_info
-
- Closed
-
-
MDEV-9925 Wrong result with aggregate function as a window function
-
- Closed
-
-
MDEV-10859 Wrong result of aggregate window function in query with HAVING and no ORDER BY
-
- Closed
-
-
MDEV-10861 Window functions tests are non-deterministic (prone to sporadic failures)
-
- Closed
-
-
MDEV-10875 Assertion `join->group_list || !join->is_in_subquery()' failed on subquery with window function
-
- Closed
-
-
MDEV-10885 Server crashes in Field::is_null / Protocol_text::store
-
- Closed
-
-
MDEV-11138 Server crashes in JOIN::make_aggr_tables_info on SELECT ROW_NUMBER() OVER ()
-
- Closed
-
-
MDEV-11139 Feature_window_functions counts queries, not functions
-
- Open
-
-
MDEV-11745 Wrong results upon using window function with min/max aggregation
-
- Closed
-
-
MDEV-11746 Wrong result upon using FIRST_VALUE with a window frame
-
- Closed
-
-
MDEV-11747 Suspicious limitation for RANGE frames
-
- Open
-
-
MDEV-15837 Assertion `item1->type() == Item::FIELD_ITEM && item2->type() == Item::FIELD_ITEM' failed in compare_order_elements function
-
- Closed
-
-
MDEV-9894 Assertion `0' failed in Window_func_runner::setup
-
- Closed
-
-
MDEV-9895 Assertion `n_rows > 0' failed in Frame_cursor* get_frame_cursor
-
- Closed
-
-
MDEV-10097 Assertion `count > 0' failed in Item_sum_sum::add_helper(bool)
-
- Closed
-
-
MDEV-10860 Mix of aggregate window functions and GROUP BY produces confusing results
-
- Confirmed
-
Note 1
<window frame preceding> ::= <unsigned value specification> PRECEDING
<unsigned value specification> ::= <unsigned literal> | <general value specification>
<general value specification> ::= <host parameter specification> | <SQL parameter reference> | <dynamic parameter specification> | <embedded variable specification> | <current collation specification> | CURRENT_CATALOG | CURRENT_DEFAULT_TRANSFORM_GROUP | CURRENT_PATH | CURRENT_ROLE | CURRENT_SCHEMA | CURRENT_TRANSFORM_GROUP_FOR_TYPE <path-resolved user-defined type name> | CURRENT_USER | SESSION_USER | SYSTEM_USER | USER | VALUE
Standard allows variables in <window frame preceding>, in MariaDB only literals seem to be allowed? - to document