When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.

The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.

If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.

When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y.

Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.

When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y.

TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND). 

VALUES is now supported as a standalone command and as a table source: SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;

The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.

The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.

Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly.

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.