Add support for persisting OffsetDateTime/ZonedDateTime [DATAJDBC-414]

[spring-projects-issues]

Milan Milanov opened DATAJDBC-414 and commented

Currently the supported date types are only java.util.Date, java.time.LocalDate, java.time.LocalDateTime and java.time.LocalTime. This could be improved by adding built-in converters for the java.time.OffsetDateTime and java.time.ZonedDateTime, as they both provide actual moments in time as opposed to their Local alternatives. They are also generic and widely used java.time types

---

Issue Links:

• DATAJDBC-443 Add database dependent simple types

[spring-projects-issues]

Milan Milanov commented

Again Jens Schauder, i'd be happy to try and tackle this, with the necessary guidance :)

[spring-projects-issues]

Jens Schauder commented

I don't want to add logic for Zoned* variants of date and time types.
In almost all cases we have seen, the timezone should not be tied to the date type, but some other object (the location where an event is happening, the location where a user is located ..) and therefore stored separately.

The combination of a date/time with a timezone is then really part of the presentation layer.

If you want to represent a point in time Instant is most often the right time to use at least on the persistence side of things which is also supported by Spring Data JDBC.

If your database/JDBC driver directly supports Zoned* types you should be able to register it as a simple type.
Doing so for databases that support it would be a valid issue/PR.

[Hronom]

Hey what type to use with PostgreSQL TIMESTAMP WITH TIME ZONE?

For example use them for technical fields like created_at/updated_at, when this fields helps during debug to understand when an entity was created/updated.

When we use JDBI we can use ZonedDateTime, but with Spring JDBC - not. So basically we need to switch and use JDBI instead of Spring JDBC?