[MDEV-9979] Keywords UNBOUNDED, PRECEDING, FOLLOWING, TIES, OTHERS should be non-reserved Created: 2016-04-25  Updated: 2017-01-31  Resolved: 2017-01-31

Status: Closed
Project: MariaDB Server
Component/s: Optimizer, Parser
Affects Version/s: 10.2
Fix Version/s: 10.2.4

Type: Bug Priority: Major
Reporter: Alexander Barkov Assignee: Alexander Barkov
Resolution: Fixed Votes: 0
Labels: 10.2-rc, regression

Issue Links:
Relates
relates to MDEV-11878 Shift/reduce conflict in window_spec ... Closed
Sprint: 10.2.4-1, 10.2.4-2

 Description   

These queries:

SELECT 1 AS UNBOUNDED;
 
SELECT 1 AS PRECEDING;
 
SELECT 1 AS FOLLOWING;
 
SELECT 1 AS TIES;
 
SELECT 1 AS OTHERS;
 
SELECT 1 FROM EXCLUDE;

return a syntax error:

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'UNBOUNDED' at line 1

This is wrong. According to the standard, these keywords must be non-reserved.

All these queries worked fine in 10.1. So this is a regression.

This query correctly fails:

SELECT 1 FROM WINDOW;

as WINDOW is a reserved keyword, according to the standard.

 Comments   
Comment by Vicențiu Ciorbaru [ 2017-01-31 ]

Ok to push, with the mention that it should say the standard version that marks the keywords as non-reserved.

Generated at Thu Feb 08 07:38:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.