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

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.

Issue 279: Auto-Server mode: unclear error message when trying to connect using AUTO_SERVER if the database is already open without the flag (Connection is broken: "null").

CSVREAD / CSVWRITE: instead of setting the options one by one, all options can be combined into a space separated key-value pairs.

New database setting OPTIMIZE_IN_SELECT (enabled by default for version 1.3.x). If enabled, IN(SELECT...) conditions are faster if there are many rows in the table or subquery.

Investigate why closing a file sometimes takes 45 seconds (see also http://stackoverflow.com/questions/4760809/closing-a-randomaccessfile-sometimes-takes-exactly-45-seconds)

Investigate why closing a file sometimes takes 45 seconds (see also http://stackoverflow.com/questions/4760809/closing-a-randomaccessfile-sometimes-takes-exactly-45-seconds)

TCP Server: a base directory with a prefix with a database name with prefix didn't work as expected (this only applies to non-disk and wrapped file systems).

Version 1.3: when re-running the same query so that the previous result was re-used, and if the result set was large so that it was stored externally (in a temp file or in a temp table), then reading rows from both result sets resulted in an exception or wrong behavior.

A new sample application that shows how to create a read-only database in a zip file where the database file is split into multiple smaller parts.

The wrong error message was thrown when trying to open a database where the database file could not be read for some reason (for example because the split file system was used, and the file was split at the wrong position). 

The wrong error message was thrown when trying to open a database where the database file could not be read for some reason (for example because the split file system was used, and the file was split at the wrong position). 

The scan-resistant cache type "TQ" (two queue) is again available. To use it, append ;CACHE_TYPE=TQ to the database URL.

The scan-resistant cache type "TQ" (two queue) is again available. To use it, append ;CACHE_TYPE=TQ to the database URL.