Hello,

when writing Calendar values we experienced, that all values are written in the wrong timezone to the database. All values were shifted by an offset, which is related to the original timezone of the Calendar object. This behavior is critical, since we can’t control by 100% the Calendar values by ourself. We tried to use the jdbcTimeZone settings as well the user.timeZone setting - nothing worked for use.

The root cause is related to the TimestampTypeDescriptor (getBinder, doBind). In both methods the Calendar type has a special handling. The configured jdbcTimezon is ignored and the reference timezon for storing the data is taken from the Calendar object itself. Based on the nature of the Calendar object, this is critical. As timestamp with timezone the offset should apply and at least the default timezone should be used. The current handling is an appraoch, which is correct for local time (LocalDateTime),

Solution: at least the jdbcTimezone should also apply to the Calendar type. If jdbcTimezone is not specified the configured default timezone should being used as 3rd parameter for PreparedStatement.setTimeStamp and CallableStatement::setTimestamp.

Thanks a lot for all Your hibernate support and the excellent ORM solution.

Best regards,

Matthias