Password hash: in addition to connecting with the plain text password, H2 now supports connecting with the password hash.

The native fulltext search could cause a Java level deadlock if searching from multiple connections concurrently.

Server mode: if the client ran with a different timezone setting than the server, date values got shifted by the difference between the timezones.

MVCC: when trying to insert two rows with the same key from two connections, the second connection immediately threw the exception "Unique index or primary key violation".

MVCC: when trying to insert two rows with the same key from two connections, the second connection immediately threw the exception "Unique index or primary key violation".

Server mode: if the client ran with a different timezone setting than the server, date values got shifted by the difference between the timezones.

The built-in connection pool (JdbcConnectionPool) did not always honor the login timeout (the timeout could occur much too early).

The table INFORMATION_SCHEMA.SETTINGS now contains all H2-specific system properties that are explicitly set.

Data modifications (inserts, updates, and deletes) are now faster for existing tables because converting objects to byte arrays is avoided if possible.

It is now allowed to truncate a table if referential integrity has been disabled for this table or database.

It is now allowed to truncate a table if referential integrity has been disabled for this table or database.

The cache was not used efficiently when reading (behaving like a FIFO cache instead of an LRU cache).