Consider hibernate.timezone.default_storage for OffsetTime typing and storage
Description
As documented (and implemented), hibernate.timezone.default_storage affects ZonedDateTime and OffsetDateTime, but not OffsetTime.
As a result, if you set hibernate.timezone.default_storage=NORMALIZE_UTC or hibernate.timezone.default_storage=COLUMN or hibernate.timezone.default_storage=NATIVE, it won’t affect OffsetTime properties, which will still be mapped to a column of type TIME (not TIME WITH TIMEZONE), and will still be normalized to hibernate.jdbc.time_zone or the JVM timezone (not UTC).
That’s at least surprising, and I think getting OffsetTime in line with ZonedDateTime and OffsetDateTime would improve the situation.
As documented (and implemented),
hibernate.timezone.default_storage
affectsZonedDateTime
andOffsetDateTime
, but notOffsetTime
.As a result, if you set
hibernate.timezone.default_storage=NORMALIZE_UTC
orhibernate.timezone.default_storage=COLUMN
orhibernate.timezone.default_storage=NATIVE
, it won’t affectOffsetTime
properties, which will still be mapped to a column of typeTIME
(notTIME WITH TIMEZONE
), and will still be normalized tohibernate.jdbc.time_zone
or the JVM timezone (not UTC).That’s at least surprising, and I think getting
OffsetTime
in line withZonedDateTime
andOffsetDateTime
would improve the situation.