Archive: Support for UTC-related Oracle issues - #3905
Draft
kasemir wants to merge 1 commit into
Draft
Conversation
Allow customization of the raw data query, with option to pass the start and end time of the raw data query as a UTC-based "local" time.
kasemir
marked this pull request as draft
August 4, 2026 18:26
|
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
1 participant
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.
The
sql.Timestamp, just likeInstant,Date, ... internally holds seconds-since-epoch.There are various ways to convert between local time zones, and RDBs like MySQL or Postgres handle this well.
Oracle, however, may treat the
Timestampas a local time zone reading. This PR allows customization of the raw data query, with an option to pass the start and end time of the raw data query as a UTC-based "local" time.