Fix: Add getAvailableValues for enum to Postgres parser; #22
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
rokmohar
changed the title
rokmohar
changed the title
rokmohar
changed the title
rokmohar
force-pushed
the
fix/postgres-get-available-values
branch
2 times, most recently
from
beae0a4
to
097ef9e
Compare
rokmohar
force-pushed
the
fix/postgres-get-available-values
branch
from
097ef9e
to
49e070c
Compare
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.
This enables the Postgres parser to load available enum values for user defined types; This solves issue with filters for enum values. The error happened becuase of
ilikecomparison on custom data type for enum.