Hello. 1. 1.4.200 was the last release in 1.4 series of releases and upcoming 2.0.202 has significant changes everywhere and shouldn't be considered as drop-in replacement, you may need some adjustments for it.
2. We have some known unintended regressions that need to be fixed before the release of H2 2.0, so the release is delayed until they will be fixed. There is no exact timeline. 3. 1.4.200 definitely has a bug, but I have no idea why you ever use `ResultSet.getTimestamp()` on a `TIME` column. Applications normally use ResultSet.getObject(column, LocalTime.class) (this is the best choice for H2) or legacy ResultSet.getTime(column) (has problems at least in one time zone due to own design flaws of java.sql.Time). Even more, conversion from TIME to TIMESTAMP was aligned with the SQL Standard in H2 1.4.200 (due to bug in JDBC layer in this version you need to use CAST directly in the SQL code to see how it works). This conversion in not compatible with old versions of H2 anyway. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/ca43af43-4ab1-470a-a607-06884cab1354o%40googlegroups.com.
