fix: allowing skyline keywords as columns, tables, etc. #2137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following on from this PR -> #2078
Associated to this issue -> #2136
The keywords LOW, HIGH, PLUS and INVERSE were missing from line 2048 of
JSqlParserCC.jjt
as they were added as new restricted keywords. I have added them manually to line 2048 and removed them as restricted keywords.I could have done the same with PREFERRING, but since #2078 was merged its become an important new keyword like WHERE, so Ive left it out.