Avoid "warning: [unchecked] Possible heap pollution from parameterized vararg type" (should use @SafeVarargs, but Java 6 doesn't support that yet)

MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.

MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.

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).

The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.

Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.