Native fulltext search: the characters '<', '>', and '\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)

The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.

The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.

When reading from the classpath (for example read_file('classpath:logo.png')), now the content class loader is used if the resource can't be found otherwise.

The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries.

A read only database with writeable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.

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))".

There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).

Split file system: truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.

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.