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.

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.

More accurate calculation of variance and standard deviation for large number of samples with low variance (now using Welford's method).

More accurate calculation of variance and standard deviation for large number of samples with low variance (now using Welford's method).

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.