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.

When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).

When the system property h2.lobInDatabase is set, the lob tables were always created when closing the database, even if the tables were not needed.

In the MySQL mode, SHOW TABLES didn't work, and meta data tables were not case insensitive. Updateable result sets didn't work as expected. Issue 249.