MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.

Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".

When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NPE), now a clear error message is shown.

Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".

Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.

Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".

A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.

A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.

The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.

Avoid "warning: [unchecked] Possible heap pollution from parameterized vararg type" (should use @SafeVarargs, but Java 6 doesn't support that yet)

MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.

MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.