Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.

Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.

Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.

A new class org.h2.tools.TriggerAdapter allows to use the ResultSet interface within trigger implementations.

When killing the process while the database was writing a checkpoint or while it was closing, the database could become corrupt. (improved tests)

When killing the process while the database was writing a checkpoint or while it was closing, the database could become corrupt. (work in progress)

When killing the process while the database was writing a checkpoint or while it was closing, the database could become corrupt. (work in progress)

Queries using multiple IN(..) conditions on the same table could cause repeated rows in the result set.

There was a possible Java level deadlock when opening an uninitialized database and using a file system that also opened a database.

When killing the process while the database was writing a checkpoint or while it was closing, the database could become corrupt. (work in progress)

Translation: Lubomir Grajciar translated the H2 Console as well as all error message to Slovensky. Thanks a lot!

There was a possible Java level deadlock when opening an uninitialized database and using a file system that also opened a database.