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

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.

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.

Linked tables: for DECIMAL column, Oracle reports precision 0 and scale -127. A workaround has been implemented.

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.