users@jpa-spec.java.net

[jpa-spec users] Re: JPA_SPEC-63

From: Lance Andersen <lance.andersen_at_oracle.com>
Date: Thu, 4 May 2017 15:05:00 -0400

> On May 4, 2017, at 1:59 PM, Steve Ebersole <steve_at_hibernate.org> wrote:
>
> So long as we are not requiring providers to chose TIMESTAMP_WITH_TIMEZONE/TIME_WITH_TIMEZONE as the mapping for java.time.OffsetDatetime/java.time.OffsetTime then that text looks good to me. Also, why no support for java.time.Zoned* variants?
>

FWIW

For JDBC we decided to just support TIMESTAMP with LocalDateTime and TIME with LocalTime as the SQL Standard does require Time Zone support unless “WITH TIMEZONE” is specified.

TIMESTAMP_WITH_TIMEZONE it was felt that OffsetDateTime was the best mapping after various discussions (for databases that support TIMEZONE)

I do realize that Hibernate supports OffsetDateTime for TIMESTAMP as well. This is certainly allowed by the JDBC spec just not required.

There was not any desire by the driver vendors/EG to support ZonedDateTime at the time but we could add standard support in JDBC.next if that changes

HTH

Best
Lance
 <http://oracle.com/us/design/oracle-email-sig-198324.gif>
 <http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif>
 <http://oracle.com/us/design/oracle-email-sig-198324.gif>Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen_at_oracle.com <mailto:Lance.Andersen_at_oracle.com>