Any advantage in using LocalDateTime binding

[Silvio]

H2 supports preparedStatement.setObject(n,localDateTimeValue) and resultSet.getObject(n,LocalDateTime.class). I would like to know if there is any performance advantage to be gained by using this (i.e. H2 using java.time internally instead of Date/Calendar) or is it a simple wrapper around the same internal date handling functions?

[Evgenij Ryazanov]

Hello.

No, they don't use any wrappers in latest versions of H2, they all are handled by own implementations in H2.

Actually legacy java.util.* and java.sql.* data types have different bugs in Java; don't use them if you can.

Documentation of H2 also recommends JSR-310 data types:

https://h2database.com/html/datatypes.html#timestamp_type

java.time.LocalDateTime is also supported and recommended on Java 8 and later versions.

[Silvio]

Thanks for confirming that. Internally our application uses java.time almost exclusively but is converted where 3rd party APIs require so. The JDBC binding for timestamp is currently one of these cases.