Add support for pg_timestampz with UTC offsets#98
Merged
tsloughter merged 9 commits intoerleans:mainfrom Jul 1, 2025
Merged
Conversation
chiroptical
force-pushed
the
chiroptical/issue-70
branch
from
713034d to
2aec7d7
Compare
tsloughter
requested changes
Mar 8, 2025
Collaborator
tsloughter
left a comment
tsloughter
left a comment
There was a problem hiding this comment.
Add a test for a offset less than the minimum offsets and greater than the maximum to see there is a proper error. Should be for both hours and
chiroptical
force-pushed
the
chiroptical/issue-70
branch
from
977da51 to
dc0a1d9
Compare
tsloughter
approved these changes
Jul 1, 2025
Closed
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.
In this PR, I expose the timestamptz encoding of pg_types by simply bumping the version. I additionally add some tests to show the limitations.