[
https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318550#comment-17318550
]
Mark Struberg commented on OPENJPA-2865:
----------------------------------------
the only question left is how to treat {{java.time.OffsetTime}}? Right now we
map it to a {{DATE}} column in Oracle. There is no native {{TIME WITH TIME
ZONE}} type in Oracle, but only {{TIMESTAMP WITH TIME ZONE}}.
Should we rather use the laster with a fixed date pinned to {{1970-01-01}} or
keep it with {{DATE}} as we do right now?
> [Oracle] use native java.time JDBC features
> -------------------------------------------
>
> Key: OPENJPA-2865
> URL: https://issues.apache.org/jira/browse/OPENJPA-2865
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 3.1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 3.1.3
>
>
> For the supported java.time types like {{LocalDate}}, LocalDateTime,
> LocalTime, OffsetTime and OffsetDateTime we should make use of native JDBC
> driver features to avoid internal conversions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
