HSQLDB version 2.0 has three transaction control modes. It supports read committed and serializable transaction isolation levels with table level locks or with multiversion concurrency control (MVCC), or a combination of locks and MVCC. Version 1.8.1 supports transaction isolation level 0 (read uncommitted) only.5
HSQLDB has two main table types used for durable read-write data storage, i.e., if a transaction has been successfully committed, it is guaranteed that the data will survive system failure and will keep their integrity.
The default MEMORY type stores all data changes to the disk in the form of a SQL script. During engine start-up, these commands are executed and data are reconstructed into the memory.
Another table type is CACHED, which allows one to store more data, at the cost of the slower performance. The HSQLDB engine loads them only partially and synchronizes the data to the disk on transaction commits. However, the engine always loads all rows affected during an update into the memory. This renders very large updates impossible without splitting the work into smaller parts.6
Other table types allow access to comma-separated values (CSV) files. These tables can participate, for example, in queries with JOINs and simplify spreadsheet processing and read-write non-durable in-memory data storage.
HSQLDB 2.0 supports all the core features and many optional features of SQL:2008. Advanced features include user-defined SQL procedures and functions, schemas, datetime intervals, updatable views, arrays, lobs, full and lateral joins and set operations. Many non-standard functions such as TO_CHAR and DECODE are also supported. Extensions to standard SQL include user-defined aggregate functions.
Several versions of HSQLDB have been released since 2001. Early versions were based on the discontinued HypersonicSQL database engine. Version 2.0, released in 2010, is mostly new code, written to conform to Standard SQL and JDBC 4 Specification.7
Version 2.3.2 (released in 2014) is fully multi-threaded and supports high performance two-phase locking and MVCC (multiversion concurrency control) transaction control models.
"HSQLDB SQL Syntax". hsqldb.org. http://hsqldb.org/doc/2.0/guide/sqlgeneral-chapt.html ↩
"PolePosition Performance Comparison". polepos.org. http://polepos.sourceforge.net/results/html/index.html ↩
"Jitsi build 5390 release notes". Jitsi.org. Archived from the original on 2015-02-02. Retrieved 2015-02-01. https://web.archive.org/web/20150202001841/https://download.jitsi.org/jitsi/windows/updates/ ↩
"Software using HSQLDB". hsqldb.org. http://hsqldb.org/web/hsqlUsing.html ↩
"HSQLDB Documentation". hsqldb.org. http://hsqldb.org/doc/2.0/guide/sessions-chapt.html#sqlgeneral_trans_cc-sect ↩
"HSQLDB Documentation". hsqldb.org. Archived from the original on 2015-05-02. Retrieved 2007-11-11. https://web.archive.org/web/20150502215807/http://www.hsqldb.org/doc/guide/ch05.html#N10DED ↩
"The new HSQLDB". hsqldb.org. http://hsqldb.org/web/features200.html ↩