H2 Database Engine 1.1.116

H2 Database Engine 1.1.116 is very fast, open source, JDBC API Java SQL database. This feature-rich tool also has many functions.

Major Features:

1. Main Features
   • Very fast database engine
   • Open source
   • Written in Java
   • Supports standard SQL, JDBC API
   • Embedded and Server mode, Clustering support
   • Strong security features
   • The PostgreSQL ODBC driver can be used
   • Multi version concurrency
2. Additional Features
   • Disk based or in-memory databases and tables, read-only database support, temporary tables
   • Transaction support (read committed and serializable transaction isolation), 2-phase-commit
   • Multiple connections, table level locking
   • Cost based optimizer, using a genetic algorithm for complex queries, zero-administration
   • Scrollable and updatable result set support, large result set, external result sorting, functions can return a result set
   • Encrypted database (AES or XTEA), SHA-256 password encryption, encryption functions, SSL
3. SQL Support
   • Support for multiple schemas, information schema
   • Referential integrity / foreign key constraints with cascade, check constraints
   • Inner and outer joins, subqueries, read only views and inline views
   • Triggers and Java functions / stored procedures
   • Many built-in functions, including XML and lossless data compression
   • Wide range of data types including large objects (BLOB/CLOB) and arrays
   • Sequence and autoincrement columns, computed columns (can be used for function based indexes)
   • ORDER BY, GROUP BY, HAVING, UNION, LIMIT, TOP
   • Collation support, users, roles
   • Compatibility modes for IBM DB2, Apache Derby, HSQLDB, MS SQL Server, MySQL, Oracle, and PostgreSQL.
4. Security Features
   • Includes a solution for the SQL injection problem
   • User password authentication uses SHA-256 and salt
   • For server mode connections, user passwords are never transmitted in plain text over the network (even when using insecure connections; this only applies to the TCP server and not to the H2 Console however; it also doesn't apply if you set the password in the database URL)
   • All database files (including script files that can be used to backup data) can be encrypted using AES-256 and XTEA encryption algorithms
   • The remote JDBC driver supports TCP/IP connections over SSL/TLS
   • The built-in web server supports connections over SSL/TLS
   • Passwords can be sent to the database using char arrays instead of Strings
5. Other Features and Tools:
   • Small footprint (smaller than 1 MB), low memory requirements
   • Multiple index types (b-tree, tree, hash)
   • Support for multi-dimensional indexes
   • CSV (comma separated values) file support
   • Support for linked tables, and a built-in virtual 'range' table
   • EXPLAIN PLAN support, sophisticated trace options
   • Database closing can be delayed or disabled to improve the performance
   • Web-based Console application (translated to many languages) with autocomplete
   • The database can generate SQL script files
   • Contains a recovery tool that can dump the contents of the database
   • Support for variables (for example to calculate running totals)
   • Automatic re-compilation of prepared statements
   • Uses a small number of database files
   • Uses a checksum for each record and log entry for data integrity
   • Well tested (high code coverage, randomized stress tests) 

Enhancements:

• Server-less multi-connection mode: more bugs are fixed.
• The built-in help (INFORMATION_SCHEMA.HELP) is smaller, shrinking the jar file size a bit.
• H2 Console: column of tables of non-default schemas are now also listed, except for schemas starting with 'INFO'.
• ALTER TABLE: removing an auto-increment or identity column didn't remove the sequence.
• Creating indexes is now a bit faster.
• PG Server: new system property h2.pgClientEncoding to explicitly set the encoding for clients that don't send the encoding (the default encoding is UTF-8). Thanks a lot to Sergi Vladykin for the patch!
• PG Server: improved compatibility by using the type ids of the PostgreSQL driver. Thanks a lot to Sergi Vladykin for the patch!
• H2 Console: Oracle system tables are no longer listed, improving performance.
• Result sets are now read-only except if the statement or prepared statement was created with the concurrency ResultSet.CONCUR_UPDATABLE. This change is required because the old behavior (all result set are updatable) violated the JDBC spec. For backward compatibility, use the system property h2.defaultResultSetConcurrency.
• New system property h2.defaultResultSetConcurrency to change the default result set concurrency.
• JDBC: using an invalid result set type or concurrency now throws an exception.
• If a pooled connection was not closed but garbage collected, a NullPointerException could occur.
• Fulltext search: a NullPointerException was thrown when updating a value that was NULL previously.
• The Recover tool did not work with .data.db files of the wrong size.
• Triggers: if there was an exception when initializing a trigger, this exception could be hidden, and in some cases (specially when using the Lucene fulltext index mechanism) a NullPointerException was thrown later on. Now the exception that occurred on init is thrown when changing data.
• The soft-references cache (CACHE_TYPE=SOFT_LRU) could throw a NullPointerException.
• To enable the new page store mechanism, append ;PAGE_STORE=TRUE to the database URL. or set the system property h2.pageStore to true. This mechanism is still experimental, and the file format will change, but it is quite stable now.