mirror of
https://github.com/postgres/postgres.git
synced 2025-11-06 07:49:08 +03:00
Make the OVER keyword unreserved.
This results in a slightly less specific error message when OVER is used in a context where we don't accept window functions, but per discussion, it's worth it to get the benefit of not needing to reserve this keyword any more. This same refactoring will also let us avoid reserving some other keywords that we expect to add in upcoming patches (specifically, IGNORE, RESPECT, and FILTER). Troels Nielsen, with minor changes by me
This commit is contained in:
@@ -270,7 +270,7 @@ PG_KEYWORD("or", OR, RESERVED_KEYWORD)
|
||||
PG_KEYWORD("order", ORDER, RESERVED_KEYWORD)
|
||||
PG_KEYWORD("out", OUT_P, COL_NAME_KEYWORD)
|
||||
PG_KEYWORD("outer", OUTER_P, TYPE_FUNC_NAME_KEYWORD)
|
||||
PG_KEYWORD("over", OVER, TYPE_FUNC_NAME_KEYWORD)
|
||||
PG_KEYWORD("over", OVER, UNRESERVED_KEYWORD)
|
||||
PG_KEYWORD("overlaps", OVERLAPS, TYPE_FUNC_NAME_KEYWORD)
|
||||
PG_KEYWORD("overlay", OVERLAY, COL_NAME_KEYWORD)
|
||||
PG_KEYWORD("owned", OWNED, UNRESERVED_KEYWORD)
|
||||
|
||||
Reference in New Issue
Block a user