[
https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324473#comment-17324473
]
Mark Struberg commented on OPENJPA-2865:
----------------------------------------
[~rmannibucau] [~ilgrosso] wdyt? should we change the type or leave it as
{{TIMESTAMP}} for Oracle which actually does not contain a time zone? Not sure
how much OffsetTime is really used. But if so, then using a OffsetDateTime with
a fixed jan-01-1970 would be probably better?
> [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)
