The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in: "select * from dual where x in (select x from dual group by x order by max(x))".

The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.

The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.

The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.

In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.

In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.

In some cases, creating a new table or altering an existing table threw the exception: Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX".

The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL.

The sorted insert mode did not work for not-persisted tables in a persisted database. It threw a ClassCastException.

The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL.

The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.

Improved error message for syntax error: the list of expected tokens was sometimes not set correctly.

If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.

If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.