HSQLDB is a java-based relational database. It is provided under a BSD license.
HSQLDB supports most of ANSI-92 SQL and some of the SQL 99 and 2003 enhancements. HSQLDB can be run in a server mode and also embedded in a java project, making configuration and deployment extremly easy as the database "starts" with the application, when used in embedded mode.
To use HSQLDB, you only need to include the HSQLDB Jar File in your classpath (i.e., the dependency has to be declared in the Maven POM file). A call to the JDBC driver will then create an instance of the database.
HSQLDB can keep tables in various modes (independent of the runing mode: server, or embedded): By default, tables will keep all the data in-memory (but persist it to a file). This is obviously a very fast method, but not useful for larger tables. Alternatively, tables can be kept "only" on disk, which is the usual operation mode for other relational databases. Please check out the HSQLDB documentation (create table command) for details. This setting can be done on a "per-table" level, hence some tables could be kept in memory, others only on disk. This allows e.g., fine-tuning of performance. (Additionally there are also temporary tables, that are not persisted to disk at all).
The JDBC driver is initialized with a URL, e.g.
This will tell the hsqldb instance to search for a directory data/ and use the configuration pruefungen from there. This configuration name will be used for 4 files:
Especially interesting is the startup script. In the startup script, you can enter multiple SQL commands that will be run during startup. This way, you can create a certain state in your database by creating tables, adding data etc.
HSQLDB is optimized for read performance. The paramerter WRITE_DELAY tells HSQLDB to delay an update or insert statement by X msecs. This can lead to actual data-loss when the database is "turned off" without sending an appropriate shutdonw command (all data inserted after the last write to disk is lost). This often causes problems when the database is accessed within unit tests. In certain situations, it makes sense to use this delay, but for our purposes: turn it off!!
Set the write_delay to 0 by adding this line to the startup script file:
SET WRITE_DELAY 0 MILLIS