fix: Timestamp fixes for Oracle, MySQL and MariaDB #461
Conversation
This file contains 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
Owner
kagkarlsson
commented
Jan 30, 2024
•
kagkarlsson
commented
- BREAKING CHANGE: Since MySQL and MariaDB does not have a datatype for storing timestamps with time zones, start defaulting to storing them in UTC to avoid issues with DST
- BREAKING CHANGE: Change Oracle schema to use a datatype that supports time zones
… schema uses zone-aware timestamp where possible.
kagkarlsson
changed the title
kagkarlsson
changed the title
|
This branch's PR was already halfway merged. See #471 for new PR. |
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.