The pseudo-column "_ROWID_" now supports insert, update, and merge (only enabled for version 1.3.x).

The new CSV option feature introduced in version 1.3.150 didn't support spaces. Now the escape mechanism is changed to support it.

Improved error detection when starting a server with invalid arguments, such as "-tcpPort=9091" or "-tcpPort 9091" (as one parameter) instead of "-tcpPort", "9091".

The function JAVADECODE ignored characters after a non-escaped double quote. This is no longer the case.

Improved error detection when starting a server with invalid arguments, such as "-tcpPort=9091" or "-tcpPort 9091" (as one parameter) instead of "-tcpPort", "9091".

Server: it was possible to open a database outside of the base URL (if one was set). The test case was broken.

New database setting DEFAULT_CONNECTION (disabled by default) to support DriverManager.getConnection("jdbc:default:connection"). Please note the Oracle JDBC driver will try to resolve this database URL if it is loaded before the H2 driver.

CallableStatement: the first row of the result set was skipped when using CallableStatement.execute().

Issue 284: If the query cache was used (enabled by default in version 1.3.x), and multiple threads used the same connection, and the same query but different prepared statements, parameters of one prepared statement could be overwritten by another.

DatabaseMetaData.getProcedureColumns returned the wrong data (it also returned the Connection parameter if there was any).

Each table now has a pseudo-column "_ROWID_" to get the unique row id (only enabled for version 1.3.x).

Initial support to list transactions (work in progress).

Initial support to list transactions (work in progress).

For tables without a single column primary key of type INT or LONG, the unique row id had gaps, which didn't look nice.

User defined functions can now have parameters of any class. Values of type OTHER (or OBJECT or JAVA_OBJECT) are automatically de-serialized in that case.

Linked tables: for NUMERIC column, Oracle reports precision 0 and scale -127. A workaround has been implemented (the same as for DECIMAL columns in version 1.3.150).