Implement basic support for numeric and date range types #612
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
Ragnis
changed the title
|
Can we look into merging this at some point? |
|
was also implementing my own until I found this |
|
What it the status of this PR? I am interested in strange support, does this library support that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Int32RangeandInt64Rangecan be used for reading/writingint4rangeandint8rangevalues, respectivelyFloat64Rangeis useful for reading/writingnumrangevalues, when possible loss of precision is not of concern.DateRangetype can be used with the Postgresdaterangetype. This is the only one that currently supports infinite values.I'm not yet sure what would be a good way of handling the
numrangetype. Maybe by treating the min/max values as strings?