feat: Add missing (postgres) operators. #211
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The operators of posix regexp, bit string, network addresses, point, full text search, range and some missing json operators have been added. Following postgres operators precedence https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-PRECEDENCE. They have the 'binary_other' precedence rule, and to reduce the size of the parser they all produce the either token 'op_other' or 'op_unary_other'.
antoineB
force-pushed
the
feature/operators
branch
from
674c59f
to
16f299b
Compare
matthias-Q
approved these changes
Nov 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The operators of posix regexp, bit string, network addresses, point, full text search, range and some missing json operators have been added.
Following postgres operators precedence
https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-PRECEDENCE. They have the 'binary_other' precedence rule, and to reduce the size of the parser they all produce the either token 'op_other' or 'op_unary_other'.