An ArrayIndexOutOfBoundsException was thrown when querying the table information_schema.function_aliases while there are any user defined aggregate functions.

In theory, when using indexes with large index rows (or when using a very small page size), removing rows could throw an internal exception in some cases.

The default time to compact a database when closing (system property h2.maxCompactTime) is now 0.2 seconds instead of 1 second.

Inserting rows in reverse order could throw an ArrayIndexOutOfBoundsException in some cases (specially rows larger than the page size, which is 2 KB by default). Issue 226.

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.