TCP Server: a base directory with a prefix with a database name with prefix didn't work as expected (this only applies to non-disk and wrapped file systems).

A new sample application that shows how to create a read-only database in a zip file where the database file is split into multiple smaller parts.

The wrong error message was thrown when trying to open a database where the database file could not be read for some reason (for example because the split file system was used, and the file was split at the wrong position). 

The scan-resistant cache type "TQ" (two queue) is again available. To use it, append ;CACHE_TYPE=TQ to the database URL.

When the system property h2.lobInDatabase is set, reading a BLOB is a bit faster because the length is not read.

Improved date / time arithmetics. Adding and subtracting a floating point value from a date or timestamp is now supported.

When creating a BLOB with in InputStream or a CLOB with a Reader, and the InputStream or Reader threw an non-IOException, then the LOB storage was broken when storing LOBs in the database.

Cache size limit could be exceeded for certain queries, leading to an OutOfMemoryError in some cases.

Server: CLOB data with unicode characters between character code 0xd800 and 0xdfff were not transferred correctly. In many cases, the thread was stuck afterwards.

The database upgrade (to upgrade from H2 version 1.1.x) has been simplified. The setting NO_UPGRADE is no longer supported, instead use the database URL jdbc:h2v1_1:

LOB: in server mode, if the feature "LOBs in database" is disabled, the temporary files are now created in the temp directory (the same as when "LOBs in database" is enabled).

Cluster: The SQL statement SET AUTOCOMMIT FALSE doesn't work. This limitation is now documented. Issue 259.

Using the java.sql.Blob or java.sql.Clob interfaces could throw the wrong exception after the object was closed.