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.

With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data. When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.

There is a problem when opening a database file in a timezone that has different daylight saving rules

The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.

With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data. When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.

With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data. When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.

The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.

Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.

Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.

The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".

There is a problem when opening a database file in a timezone that has different daylight saving rules.

There is a problem when opening a database file in a timezone that has different daylight saving rules.