Repository navigation
docs: psqlodbc timestamptz session time zone — quirks and tracker rows - #115
Merged
Merged
Conversation
singhpratech
force-pushed
the
docs-0.1.3-timezone
branch
from
September 15, 2026 14:45
0b430c3 to
e58aa62
Compare
singhpratech
enabled auto-merge (squash)
September 15, 2026 14:46
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
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.
Records the finding behind 0.1.3 (#113) where the docs keep such things: a row in the quirks reference for the psqlodbc
SET TIME ZONE 'UTC'behaviour and its option, and an observed-finding row in the upstream tracker (psqlodbc'sSQL_C_CHARconversion oftimestamptzdrops the offset; candidate for a psqlodbc report once itsUSE_ZONEbuild option is checked). The notes page it links to goes live with the site update.