I'm going to ask this question internally to see what the other Hibernate Developers think of this Driver change.
From all the PostgreSQL references I found, it seems like everyone is suggesting to use TIMESTAMPZ instead of TIMESTAMP
, so I guess this change is understandable.
From my perspective, this change will not just affect Hibernate users, but every JDBC framework that uses PostgreSQL. We also added a hibernate.jdbc.time_zone configuration
property, so that our users can force all Timestamps to be saved in a given TimeZone, typically UTC.
I'm feeling anxious about this change since JDBC only offers a TIMESTAMP type. JDBC does not make a difference from TIMESTAMP and TIMESTAMP ith TIMEZONE, and not all DBs support this concept. For instance, MySQL makes the conversation automatically and saves all timestamps in UTC
. But then, this is probably how TIMESTAMPZ works in PostgreSQL too.
I'm going to ask this question on Twitter as well to gather more feedback from our community as well.