Add support for PostgreSQL GiST operators #17#18
Merged
Schultzer merged 1 commit intoelixir-dbvisor:mainfrom Jun 26, 2025
Merged
Add support for PostgreSQL GiST operators #17#18Schultzer merged 1 commit intoelixir-dbvisor:mainfrom
Schultzer merged 1 commit intoelixir-dbvisor:mainfrom
Conversation
Member
Hey @ibarchenkov I’ll be addressing this in my rewrite, which is coming along, almost done with the lexer. |
Contributor
Author
|
Hey Benjamin, that's great news! I'm looking forward to testing out the new version. |
Member
I've just merged #19 into main. Please let me know if you experience any issues. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR adds support for PostgreSQL GiST operators as listed here. Partially fixes #17
Note
The issue with incorrect parsing of functions (i.e., insertion of a whitespace between the function name and its parentheses) will be addressed in a separate PR.