Using the java.sql.Blob or java.sql.Clob interfaces could throw the wrong exception after the object was closed.

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 the system property h2.lobInDatabase is set, the lob tables were always created when closing the database, even if the tables were not needed.

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.

H2 Console: webAllowOthers and webSSL were swapped if they didn't exist in the properties file. Issue 244.

After a crash, the database file did not always shrink because old transaction log pages were not removed from the file.