Improved mapping of ZonedDateTime and OffsetDateTime in Hibernate 6

preview_player
Показать описание
Working with timestamps with timezone information has always been a struggle. Since Java 8 introduced the Date and Time API, the classes OffsetDateTime and ZonedDateTime have become the most obvious and commonly used types to model a timestamp with timezone information. And you might expect that choosing one of them should be the only thing you need to do.
But unfortunately, that isn’t the case if you want to persist this information in a relational database. Even though the SQL standard defines the column type TIMESTAMP_WITH_TIMEZONE, only a few databases support it. Due to that, the JPA specification doesn’t support OffsetDateTime and ZonedDateTime as attribute types. Hibernate 5 supports them by normalizing the timestamp and storing it without timezone information. Hibernate 6 improves on this and provides a clear and flexible mapping for these types.

Like my channel? Subscribe!

Want to connect with me?
  1. Thorben Janssen
  2. Hibernate
  3. Hibernate 6
  4. timezone
  5. date and time
Рекомендации по теме
Improved mapping of 0:10:21

Improved mapping of ZonedDateTime and OffsetDateTime in Hibernate 6

Hibernate Tip: What’s 0:03:22

Hibernate Tip: What’s the best way to persist a ZonedDateTime

128 - Utility 0:10:38

128 - Utility Classes - ZonedDateTime, ZoneId, OffsetDateTime

Hibernate & JPA: 0:07:42

Hibernate & JPA: Date & Time Mappings

How To Map 0:08:08

How To Map The Date And Time API with JPA 2.2

SpringBoot Postgres LocalDateTime 0:20:13

SpringBoot Postgres LocalDateTime and ZonedDateTime

DateTime API Part 0:07:50

DateTime API Part 7 - ZoneId, ZonedDateTime

The Best Mapping 0:09:07

The Best Mapping for Shared Technical Attributes With Hibernate

Hibernate you know 0:53:20

Hibernate you know it… but actually you don’t by Emmanuel Bernard

The Problem with 0:10:13

The Problem with Time & Timezones - Computerphile

How to not 0:10:45

How to not use the getResultStream method

Choosing ListSematics in 0:06:54

Choosing ListSematics in Hibernate 6

Hibernate 6 EmbeddableInstantiator 0:06:34

Hibernate 6 EmbeddableInstantiator – Instantiate embeddables your way

Hibernate you know 0:51:28

Hibernate you know it... but actually you don't by Sanne Grinovero

Hibernate Query Spaces: 0:07:18

Hibernate Query Spaces: Optimizing Flush & Cache Operations

How to use 0:01:19

How to use atZoneSameInstant method of OffsetDateTime Class? | Java 8 Date and Time

Hashing in Java 1:58:35

Hashing in Java + Java 8 Date and Time API | Map API Explained | Core Java | Day 16 | CDAC Learning

the right way 0:13:42

the right way test date & time in java

17.22 New Date 0:11:23

17.22 New Date Time Api in Java 8

Incubating Features in 0:11:27

Incubating Features in Hibernate 6

JPA Date Handling 0:14:58

JPA Date Handling - Pitfalls to Avoid (TimeZone)

OffsetDateTime in java 0:03:42

OffsetDateTime in java | Java OffsetDateTime | OffsetDateTime in java Example

Hibernate Tips ‘n’ 0:45:48

Hibernate Tips ‘n’ Tricks - 15 Tips to solve common problems by Thorben Janssen

Java 8 Features 0:03:25

Java 8 Features Part 14 - Passing Predicate To A Method

Комментарии
Автор

For the people who did upgrade to spring 3, you can revert old behaviour for time with this config; normalize

rfatcakr
Автор

You forgot to mention the Data Type of the Table column where you intend to store the ZonedDateTime Value :(

faisalsal
Автор

What a stupid mess with all this classes. How Jesus Crist i should write hibernate entities ? Should i use Date/Instant/OffsetDateTime for my datetime field or what ? Can't find normal answer, everybody write a lot of words but nobody can answer how to write simple program and not to have headache about all this timezones. Now we use plain Date class and i'm not sure when hibernate or jpa punch me in nose because of different timezone processing (when i compare date param and NOW() it goes weird, i understand why, but it too complex to maintain).

zigzag