--no commit message

When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.

When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).

When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.

When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).

When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).

When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).

When the system property h2.lobInDatabase is set, the lob tables were always created when closing the database, even if the tables were not needed.

Connection-created Clob and Blob objects can now be filled using Clob.setCharacterStream(1), Clob.setString(1, s), Blob.setBytes(1, x), Blob.setBinaryStream(1). Issue 235.

In the MySQL mode, SHOW TABLES didn't work, and meta data tables were not case insensitive. Updateable result sets didn't work as expected. Issue 249.

Connection-created Clob and Blob objects can now be filled using Clob.setCharacterStream(1), Clob.setString(1, s), Blob.setBytes(1, x), Blob.setBinaryStream(1). Issue 235.

Connection-created Clob and Blob objects can now be filled using Clob.setCharacterStream(1), Clob.setString(1, s), Blob.setBytes(1, x), Blob.setBinaryStream(1). Issue 235.

Trying to convert a very small CLOB to a BLOB or a very small CLOB to a BLOB threw a NullPointerException.

INFORMATION_SCHEMA.SETTINGS: now the current page count can be queried using select * from information_schema.settings where name = 'info.PAGE_COUNT'.

When using trace level 3, opening a database no longer prints there is a EOFException (because that is the expected behavior).

CALL calling a Java function with return type ResultSet and return value null threw a ClassCastException.