Fix datetime with timezone regression #1038
Merged
bimalkjha merged 1 commit intoibmdb:masterfrom Nov 17, 2025
Merged
Conversation
bimalkjha
approved these changes
Nov 17, 2025
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.
Support for TIMESTAMP WITH TIME ZONE was added in the last release for z/OS.
After this change, inserting timezone‑aware datetime values on LUW resulted in
overflow errors because the timezone part was being processed even though LUW
does not support TIMESTAMP WITH TIME ZONE natively.
The timezone part should not be applied for LUW. When processing datetime objects with tzinfo gives datetime overflow error.
And for zos, timestamp case timezone part should ignored. For timestamp with timezone case datetime with timezone processed.
Added fix that timezone part should be ignored for luw and should not throw error datetime overflow error.
#1030