Fix #3224 - conversion for TIME '24:00' to LocalTime breaks in binary-mode #3225
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.
All Submissions:
Changes to Existing Features:
Description
Fixes the bug described in #3224
Conversion of binary-values of
TIME
has been adapted to interpret24:00
asLocalTime.MAX
- as does conversion from text-values.As PostgreSQL only supports microsecond-precision, all values larger than
23:59:59.999_999_499
are converted toLocalTime.MAX
- as is done in other places in TimestampUtils.javaBinary test-values for TimestampUtilsTest.java are guessed, as I couldn't find a documentation / source, of how they're actually computed.