A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.

A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.

A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.

Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).

Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.

String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.

Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.

MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.

ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).

The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.