Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).

Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).

Recover tool: the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.

Read-only databases: some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.

This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection).

This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection).

This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection).

The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement: LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ

A prepared statement if type CALL that returned a result set could throw a NullPointerExecption if executed multiple times.

The following prepared statements are now cached as well: insert, update, delete, merge, and transactional commands.

The built-in connection pool is now a bit faster, specially if the system property "h2.runFinalize" is set to "false".

When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.

The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.

If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.

When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y.

Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.

When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y.