Fix compatibility with pg 9.5 and lower #11
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 automatic tlist implementation doesn't cope well with fields defined as Option, as it relies on stringify to generate the target SQL type. For now just intercept any field defined as Option<Text>, as the only problems happens in pg_aggregate.rs on pg 9.5 and below, but I should eventually find a better solution.
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 automatic tlist implementation doesn't cope well with fields defined as Option, as it relies on stringify to generate the target SQL type.
For now just intercept any field defined as Option, as the only problems happens in pg_aggregate.rs on pg 9.5 and below, but I should eventually find a better solution.