Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view.

MVStore: the Recover tool can now deal with more types of corruption in the file. MVStore: the TransactionStore now first needs to be initialized before it can be used.

Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1

The database URL setting PAGE_SIZE setting is now also used for the MVStore. MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).

The database URL setting PAGE_SIZE setting is now also used for the MVStore. MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).

MVStore: use a mark & sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.

MVStore: use a mark & sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.

In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).

Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).

Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).

Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).

Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).

In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.

In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).

In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.