Temporary Fix: Handling MySQL & SQLite timestamp columns #379
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
billy1624
force-pushed
the
issues/344-temp-fix
branch
from
b0d8d71
to
a023fd5
Compare
tyt2y3
force-pushed
the
issues/344-temp-fix
branch
from
0def824
to
8db9d10
Compare
1 task
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.
PR Info
DateTime<FixedOffset>for SQLx MySQL & SQLite sea-query#197Notes to MySQL User
MySQL user should use
sea_orm:: DateTimeWithTimeZonefor timestamp columns until SQLx upstream merged the PR (launchbadge/sqlx#1581) and released it. Only after that happened, MySQL user could usesea_orm::DateTimefor timestamp columns (#345).