Add date-time module: Instant vs LocalDateTime vs OffsetDateTime vs ZonedDateTime round-tripped across JVM time zones on H2 and PostgreSQL
Hibernate 7.4.14.Final (plus an 8.0.0.Beta4 preview run), H2 2.5.252, PostgreSQL 17.11 in Docker. Same-JVM and cross-zone round trips, @TimeZoneStorage modes, DST gap/overlap, precision (precision vs secondPrecision), hibernate.jdbc.time_zone, java_time_use_direct_jdbc default flip. Supersedes the date/time experiments of docs/13 (7.4.5); chapter 13 is unchanged. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_017ic4b7rnC7jppGGdHGESvy
This commit is contained in:
@@ -341,6 +341,7 @@ Modules with their own `pom.xml` that run plain Hibernate without the Spring Boo
|
||||
|
||||
| Module | What it covers |
|
||||
|---|---|
|
||||
| [`date-time`](date-time/) | `Instant` vs `LocalDateTime` vs `OffsetDateTime` vs `ZonedDateTime` round-tripped across JVM time zones on H2 and PostgreSQL: what survives, `@TimeZoneStorage`, DST gaps, precision, and the Hibernate 8 `java_time_use_direct_jdbc` default (Hibernate `7.4.14.Final`, Hibernate `8.0.0.Beta4` preview) |
|
||||
| [`h8-preview`](h8-preview/) | Hibernate ORM 8 beta against Hibernate 7: what breaks |
|
||||
| [`inheritance`](inheritance/) | `SINGLE_TABLE` vs `JOINED` vs `TABLE_PER_CLASS` vs `@MappedSuperclass`: generated DDL, SQL, failures and timings (Hibernate `7.4.13.Final`) |
|
||||
| [`locking`](locking/) | Optimistic (`@Version`, retries) vs pessimistic (`PESSIMISTIC_WRITE`, `NOWAIT`, `SKIP LOCKED`) locking, lost updates and deadlocks on H2 (Hibernate `7.4.14.Final`) |
|
||||
|
||||
Reference in New Issue
Block a user