[hibernate-issues] [JIRA] (HHH-16287) Consider hibernate.timezone.default_storage for OffsetTime typing and storage

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDZhYTYwODg4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16287?atlOrigin=eyJpIjoiZDZhYT... ) HHH-16287 ( https://hibernate.atlassian.net/browse/HHH-16287?atlOrigin=eyJpIjoiZDZhYT... ) Consider hibernate.timezone.default_storage for OffsetTime typing and storage ( https://hibernate.atlassian.net/browse/HHH-16287?atlOrigin=eyJpIjoiZDZhYT... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) 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}} storage 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. ( https://hibernate.atlassian.net/browse/HHH-16287#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16287#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100217- sha1:2199b34 )