Dynamically set the time zone of duckdb #853
Merged
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
|
this is fix for #852 |
JelteF
requested changes
Jul 8, 2025
JelteF
reviewed
Jul 9, 2025
JelteF
reviewed
Jul 9, 2025
JelteF
reviewed
Jul 9, 2025
JelteF
reviewed
Jul 9, 2025
Inconsistent time zone between Postgres and DuckDB can lead to unexpected results when performing some queries which use timestamptz data type. To avoid this, we should keep time zone is same during execution.
JelteF
approved these changes
Jul 10, 2025
2 tasks
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.
Inconsistent time zone between Postgres and DuckDB can lead to
unexpected results when performing some queries which use
timestamptz data type. To avoid this, we should keep time zone
same during execution.