[MDEV-9740] Window functions: catch invalid window frame specs Created: 2016-03-16 Updated: 2016-04-14 Resolved: 2016-03-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer - Window functions |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Sergei Petrunia | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Window functions: catch invalid window frame specs The standard specifies a lot of restrictions around frame definitions. We catch
in win.result, but not all. Things like "rows between 1.5 preceding and 'foo' following" are still allowed and cause assertion failures. |
| Comments |
| Comment by Sergei Petrunia [ 2016-03-17 ] | ||||||||||||||
|
The standard, section 6.10, <window function>.
MariaDB: ok (framing ignored) ORA-30486: invalid window aggregation group in the window specification
PG, MS-SQL: ok
PG, MS-SQL: OK
MariaDB: handled by the parser. One gets "Integer is required for ROWS-type frame" error. | ||||||||||||||
| Comment by Sergei Petrunia [ 2016-03-17 ] | ||||||||||||||
|
Pushed into the feature tree |