HSQLDB

From Wikipedia, the free encyclopedia

HSQLDB
Screenshot HSQL Database Manager
Latest release	1.8.0.10 / June 2, 2008
Written in	Java
OS	Cross-platform
Genre	RDBMS
License	BSD license
Website	http://hsqldb.org

HSQLDB is a relational database management system written in Java. It is based on Thomas Mueller's discontinued Hypersonic SQL Project.^[1].

HSQLDB is available under a BSD license.

It has a JDBC driver and supports a large subset of SQL-92, SQL-99, and SQL:2003 standards.^[2] It offers a fast,^[3] small (less than 100k in one version, around 600k in the standard version) database engine which offers both in-memory and disk-based tables. Embedded and server modes are available.

Additionally, it includes tools such as a minimal web server, in-memory query and management tools (can be run as applets), and a number of demonstration examples. It can run on Java runtimes from version 1.1 upwards, including free Java runtimes such as Kaffe.

HSQLDB is currently being used as a database and persistence engine in many open source software projects, such as OpenOffice.org Base and the Standalone Roller Demo,^[4] as well as in commercial products, such as Mathematica or InstallAnywhere (starting with version 8.0).^{[citation needed]}

Over 250 book titles document the use of HSQLDB for application development with frameworks such as Spring Framework or Hibernate. ,^[5]

1 Transaction support
2 Data storage
3 See also
4 References
5 External links

[edit] Transaction support

HSQLDB supports transaction isolation level 0 (read uncommitted) only. It means, an SQL query in one session might occasionally fetch uncommitted data from another session.^[6] According to the official web site news section, "a separate version with multiversion row concurrency control was successfully developed and has undergone internal tests. This will be released as version 2.0". There is no information on when it will be available.

[edit] Data storage

HSQLDB has two main table types used for durable read-write data storage (i.e. if transaction has been successfully committed, it is guaranteed that the data will survive system failure and will keep its integrity).

The default MEMORY type stores all data changes to the disk in the form of an SQL script. During engine start up, these commands are executed and data is reconstructed into the memory. While this behavior is not suitable for very large tables, it provides highly regarded performance benefits and is easy to debug.

Another table type is CACHED and it allows to store gigabytes of data, at a cost of the slower performance. 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. It renders very large updates impossible without splitting the work in smaller parts.^[7]

Other table types allow for read-write CSV-file access (these tables can participate, for example, in queries with JOINs and simplify spreadsheet processing) and read-write non-durable in-memory data storage.

[edit] See also

[edit] References

This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (February 2008)

This article or section needs sources or references that appear in reliable, third-party publications.
Primary sources and sources affiliated with the subject of the article are generally not sufficient for a Wikipedia article. Please include more appropriate citations from reliable sources, or discuss the issue on the talk page.
This article has been tagged since February 2008.