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

Opening a database with a corrupt split file must lead to a database exception, not a "Database may be already in use" exception

There was a memory leak in the trace system. Opening and closing many connections could run out of memory.

Server tool: the tcpShutdown feature now also stops other servers (web server and PostgreSQL server).

Lob in database: after the process was killed while adding a lob, inserting a lob could throw an exception (primary key violation in LOB_MAP).

Lob in database: after the process was killed while adding a lob, inserting a lob could throw an exception (primary key violation in LOB_MAP).

Server tool: the tcpShutdown feature now also stops other servers (web server and PostgreSQL server).

Server tool: the tcpShutdown feature now also stops other servers (web server and PostgreSQL server).

Multi-version concurrency: SELECT ... FOR UPDATE threw a "concurrent update" exception immediately instead of a "lock timeout" exception after the set lock timeout if the row was already locked by another connection.

Translation: the H2 Console and error messages have been translated to Czech by Hannibal (http://hannibal.cestiny.cz/). Thanks a lot!

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

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

Issue 269: GROUP BY queries with a column or having clause that contains IN(SELECT ...) could return the wrong values. Example: SELECT X IN(SELECT Y) FROM Z GROUP BY X.

After closing a database, the writer thread will stop almost immediately (instead of after at most 100 ms). This should avoid error messages in the Tomcat log file after a shutdown.

Issue 271: ResultSet.getConcurrency() did not correctly detect that the result set is not updatable.

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.

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.