Skip to content

fix(mysql): datetime/time are encoded longer than necessary - #4541

Open
Skgland wants to merge 2 commits into
transact-rs:mainfrom
Skgland:issue-4540
Open

Skgland wants to merge 2 commits into
transact-rs:mainfrom
Skgland:issue-4540

Conversation

@Skgland

@Skgland Skgland commented Nov 20, 2026

Copy link
Copy Markdown

Does your PR solve an issue?

fixes #4540

Is this a breaking change?

No. The same encoding is already used for DateTime/Time values with zero submicrosecond nanosecond and the tests verify this.

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.

MySql Chrono NaiveDateTime checks nanoseconds instead of microseconds resulting in encoding longer than necessary

1 participant