MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table.

For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.

getTimeTry() was never being passed a null timezone, so don't check for that. Rather check if the timezone is still the default, so we can use the local cached Calendar.

Fix error message (running "./build.sh docs" automatically adds missing translations, so the only file that needs to be changed manually is _message_en.prop, and then the other files only when translating; untranslated entries have a # as the first character in the value)

"Bump up the sequence cache size from 64 to 1024.
 Prevents sequence writing from becoming a bottleneck when doing bulk load."

Prevents sequence writing from becoming a bottleneck when doing bulk load.

We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.

In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.

Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).