fix: decode postgres time without subsecond #2784
Merged
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.
This resolves #2707
The cause of the issue
The issue is caused by Postgres.
Specifically, when we select
0:0:0.123
from Postgres, it properly returns00:00:00.123
.However, in the case of selecting
0:0:0.0
, it returns00:00:00
, removing after the.0
.This leads to the error
Decode(ParseFromDescription(InvalidLiteral)
, because it does not match theTime
format.To solve this, I implemented the same logic as
datetime
.