Skip to content

Sqlite chrono::DateTime<FixedOffset> timezone fix#1618

Merged
abonander merged 1 commit intolaunchbadge:masterfrom
05storm26:sqlite-timezone-fix
Apr 14, 2022
Merged

Sqlite chrono::DateTime<FixedOffset> timezone fix#1618
abonander merged 1 commit intolaunchbadge:masterfrom
05storm26:sqlite-timezone-fix

Conversation

@05storm26
Copy link
Copy Markdown
Contributor

Fixes: #1617

@05storm26 05storm26 force-pushed the sqlite-timezone-fix branch 3 times, most recently from 42f0486 to 072a2b9 Compare January 10, 2022 11:49
@05storm26 05storm26 force-pushed the sqlite-timezone-fix branch from 072a2b9 to c5832d9 Compare January 10, 2022 11:50
@05storm26
Copy link
Copy Markdown
Contributor Author

@abonander When can you merge this? Is this going to be in 0.6?

@abonander
Copy link
Copy Markdown
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chrono::DateTime<FixedOffset> doesn't store the offset (timezone) in sqlite as text and timezone information is lost

2 participants