Branch: refs/heads/master Home: https://github.com/hibernate/hibernate-orm Commit: 352b029404877822468738e693136e9a5ced6342 https://github.com/hibernate/hibernate-orm/commit/352b029404877822468738e... Author: Gail Badner <gbadner(a)redhat.com&gt; Date: 2019-07-24 (Wed, 24 Jul 2019) Changed paths: M hibernate-core/src/test/java/org/hibernate/test/type/AbstractJavaTimeTypeTest.java M hibernate-core/src/test/java/org/hibernate/test/type/OffsetTimeTest.java Log Message: ----------- Revert "HHH-13266 HHH-13357 : Skip OffsetTimeTest#nativeWriteThenRead and #writeThenRead in some cases due to HHH-13357" This reverts commit b7b8f44298191db050f12819ca0594a30124df75. Commit: 0f4c7ec0f2f1cb1d822ab37b6b14707a14951685 https://github.com/hibernate/hibernate-orm/commit/0f4c7ec0f2f1cb1d822ab37... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2019-07-24 (Wed, 24 Jul 2019) Changed paths: M hibernate-core/src/main/java/org/hibernate/type/descriptor/java/OffsetTimeJavaDescriptor.java Log Message: ----------- HHH-13357 Fix OffsetDateTime ending up with a different offset than the JVM default when loading from a Timestamp This bug only affects users that override the type descriptor for OffsetDateTime, and only affects reading. Since I had to change how we extract the local time from the timestamp, I also took this opportunity to apply the fix for HHH-13266, which should make data loading more resilient when databases contain weird values representing time, like 1650-04-15T14:45:49 or 0000-00-00T14:45:49. Compare: https://github.com/hibernate/hibernate-orm/compare/18f9c142e375...0f4c7ec...