Repository navigation
[8.0] Truncate sub-microsecond ticks when formatting TimeSpan as interval - #3948
Merged
Merged
Conversation
This file contains hidden or 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
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.
Backport of #3932.
Fixes #3926.
Truncate sub-microsecond TimeSpan ticks before formatting PostgreSQL intervals, preventing trailing decimal separators and negative zero. Includes the original SQL-literal and JSON reader/writer regression coverage; the shared NodaTime Duration formatter benefits automatically. No 8.0 compatibility adaptations were necessary.
Validation:
dotnet test test/EFCore.PG.Tests/EFCore.PG.Tests.csproj --no-restore --filter FullyQualifiedName~NpgsqlTypeMappingTest— 112 passed, 6 existing skips. Restore used a temporary local feed containing the exact configured 8.0.6 packages after NuGet resolution failed; dependency versions and repository configuration are unchanged.