Sqlite chrono::DateTime<FixedOffset> timezone fix #1618
Merged
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
05storm26
force-pushed
the
sqlite-timezone-fix
branch
3 times, most recently
from
42f0486
to
072a2b9
Compare
05storm26
force-pushed
the
sqlite-timezone-fix
branch
from
072a2b9
to
c5832d9
Compare
|
@abonander When can you merge this? Is this going to be in 0.6? |
|
I'm currently working on a 0.5.11 release so I can't say when 0.6.0 is coming out. Since this changes the format that timestamps serialize to in an observable way, I think this is technically a breaking change and would have to be part of 0.6.0. |
This was referenced Jun 21, 2022
6 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.
Fixes: #1617