MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.

StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.

all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).

Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.

MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).

In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1

In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;

the logic that cleared the flag could never be reached, resulting in performance degradation.
Reported by Alexander Nesterov.

In version 1.3.183, indexes that contains columns with a default value generated by a sequence where not used. This includes identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.

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.

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.

Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations