Add OffsetDateTime and Instant converters #38
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.
I wanted all my
TIMESTAMP_WITH_TIMEZONE
columns to beInstants
rather thanOffsetDateTimes
(I presumeOffsetDateTime
is default for the typeTIMESTAMP_WITH_TIMEZONE
in postgres). So I created a converter of the typeConverter<OffsetDateTime, Instant>
that convertedTIMESTAMP_WITH_TIMEZONE
types to Instants. I.e.OffsetDateTimes
toInstants
.However, this resulted in a
ClassCastException: String cannot be converted to OffsetDateTime
stemming from theconverter.from(OffsetDateTime)
method in AbstractAsyncQueryExecutor.It was trying to force a string type into the
from
method of my converter, where it should have been anOffsetDateTime
.This PR fixes that problem by introducing bindings to the
OffsetDateTime
andInstant
types and so therefore allowsOffsetDateTime
andInstant
types to be retrieved from databases.Thanks 👍