fix(postgres): handle case sensitive table names #408
Conversation
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
According to postgres documentation, fetching the oid of a relation using ::regclass requires specific handling for case matching, as described in https://www.postgresql.org/docs/current/datatype-oid.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
According to postgres documentation, fetching the oid of a relation using ::regclass requires specific handling for case matching, as described in https://www.postgresql.org/docs/current/datatype-oid.html
Disclaimer: due to how the generation files are made, I was not able to properly use them without it removing several things (I don't have any oracle/sqlserver running locally), so I updated manually the generated files based on what the gen.sh actually does.
Feel free to update the PR if needed