You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by am...@apache.org on 2019/04/30 10:15:33 UTC
[ignite] 17/17: GG-18539: Remove useless code.
This is an automated email from the ASF dual-hosted git repository.
amashenkov pushed a commit to branch gg-18539
in repository https://gitbox.apache.org/repos/asf/ignite.git
commit 6175879bd69b83aaa79a714146914b356d787b08
Author: Andrey V. Mashenkov <an...@gmail.com>
AuthorDate: Tue Apr 30 13:13:31 2019 +0300
GG-18539: Remove useless code.
---
modules/h2/pom.xml | 7 -
modules/h2/src/docsrc/html/advanced.html | 1968 ---
modules/h2/src/docsrc/html/architecture.html | 154 -
modules/h2/src/docsrc/html/build.html | 325 -
modules/h2/src/docsrc/html/changelog.html | 1487 ---
modules/h2/src/docsrc/html/cheatSheet.html | 216 -
modules/h2/src/docsrc/html/commands.html | 179 -
modules/h2/src/docsrc/html/datatypes.html | 99 -
modules/h2/src/docsrc/html/download.html | 76 -
modules/h2/src/docsrc/html/faq.html | 288 -
modules/h2/src/docsrc/html/features.html | 1719 ---
modules/h2/src/docsrc/html/fragments.html | 130 -
modules/h2/src/docsrc/html/frame.html | 40 -
modules/h2/src/docsrc/html/functions.html | 324 -
modules/h2/src/docsrc/html/grammar.html | 178 -
modules/h2/src/docsrc/html/history.html | 182 -
.../html/images/connection-mode-embedded-2.png | Bin 48466 -> 0 bytes
.../html/images/connection-mode-embedded.png | Bin 20407 -> 0 bytes
.../docsrc/html/images/connection-mode-mixed-2.png | Bin 70685 -> 0 bytes
.../docsrc/html/images/connection-mode-mixed.png | Bin 31588 -> 0 bytes
.../html/images/connection-mode-remote-2.png | Bin 58248 -> 0 bytes
.../docsrc/html/images/connection-mode-remote.png | Bin 25020 -> 0 bytes
modules/h2/src/docsrc/html/images/console-2.png | Bin 68604 -> 0 bytes
modules/h2/src/docsrc/html/images/console.png | Bin 29569 -> 0 bytes
modules/h2/src/docsrc/html/images/db-16.png | Bin 547 -> 0 bytes
modules/h2/src/docsrc/html/images/db-64-t.png | Bin 11867 -> 0 bytes
modules/h2/src/docsrc/html/images/download-2.png | Bin 2673 -> 0 bytes
modules/h2/src/docsrc/html/images/download.png | Bin 745 -> 0 bytes
modules/h2/src/docsrc/html/images/h2-logo-2.png | Bin 4810 -> 0 bytes
modules/h2/src/docsrc/html/images/h2-logo.png | Bin 3361 -> 0 bytes
.../h2/src/docsrc/html/images/h2-logo_square.png | Bin 2330 -> 0 bytes
.../h2/src/docsrc/html/images/icon_disconnect.gif | Bin 114 -> 0 bytes
modules/h2/src/docsrc/html/images/language_de.png | Bin 240 -> 0 bytes
modules/h2/src/docsrc/html/images/language_en.gif | Bin 268 -> 0 bytes
modules/h2/src/docsrc/html/images/language_ja.gif | Bin 685 -> 0 bytes
modules/h2/src/docsrc/html/images/mail-support.png | Bin 756 -> 0 bytes
.../h2/src/docsrc/html/images/paypal-donate.png | Bin 6172 -> 0 bytes
modules/h2/src/docsrc/html/images/performance.png | Bin 2343 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-1.png | Bin 13911 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-2.png | Bin 3765 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-3.png | Bin 11783 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-4.png | Bin 30387 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-5.png | Bin 36043 -> 0 bytes
modules/h2/src/docsrc/html/images/quickstart-6.png | Bin 31108 -> 0 bytes
modules/h2/src/docsrc/html/images/screenshot.png | Bin 16894 -> 0 bytes
modules/h2/src/docsrc/html/installation.html | 122 -
modules/h2/src/docsrc/html/license.html | 404 -
modules/h2/src/docsrc/html/links.html | 708 --
modules/h2/src/docsrc/html/main.html | 46 -
modules/h2/src/docsrc/html/mainWeb.html | 195 -
modules/h2/src/docsrc/html/mvstore.html | 749 --
modules/h2/src/docsrc/html/navigation.js | 195 -
modules/h2/src/docsrc/html/performance.html | 893 --
modules/h2/src/docsrc/html/quickstart.html | 105 -
modules/h2/src/docsrc/html/roadmap.html | 532 -
modules/h2/src/docsrc/html/search.js | 273 -
modules/h2/src/docsrc/html/source.html | 52 -
modules/h2/src/docsrc/html/sourceError.html | 252 -
modules/h2/src/docsrc/html/stylesheet.css | 379 -
modules/h2/src/docsrc/html/stylesheetPdf.css | 154 -
modules/h2/src/docsrc/html/systemtables.html | 63 -
modules/h2/src/docsrc/html/tutorial.html | 1502 ---
.../docsrc/images/connection-mode-embedded-2.png | Bin 48466 -> 0 bytes
.../src/docsrc/images/connection-mode-mixed-2.png | Bin 70685 -> 0 bytes
.../src/docsrc/images/connection-mode-remote-2.png | Bin 58248 -> 0 bytes
modules/h2/src/docsrc/images/connection-modes.svg | 1118 --
modules/h2/src/docsrc/images/console-2.png | Bin 68604 -> 0 bytes
modules/h2/src/docsrc/images/console.png | Bin 29569 -> 0 bytes
modules/h2/src/docsrc/images/console.svg | 515 -
modules/h2/src/docsrc/images/db-16.png | Bin 547 -> 0 bytes
modules/h2/src/docsrc/images/db-22.png | Bin 1239 -> 0 bytes
modules/h2/src/docsrc/images/db-24.png | Bin 574 -> 0 bytes
modules/h2/src/docsrc/images/db-32.png | Bin 1399 -> 0 bytes
modules/h2/src/docsrc/images/db-64-t.png | Bin 11867 -> 0 bytes
modules/h2/src/docsrc/images/db.svg | 308 -
modules/h2/src/docsrc/images/download-2.png | Bin 2673 -> 0 bytes
modules/h2/src/docsrc/images/download.png | Bin 745 -> 0 bytes
modules/h2/src/docsrc/images/download.svg | 125 -
modules/h2/src/docsrc/images/favicon.ico | Bin 4286 -> 0 bytes
modules/h2/src/docsrc/images/h2-16.png | Bin 675 -> 0 bytes
modules/h2/src/docsrc/images/h2-24.png | Bin 995 -> 0 bytes
modules/h2/src/docsrc/images/h2-32.png | Bin 1362 -> 0 bytes
modules/h2/src/docsrc/images/h2-64.png | Bin 2718 -> 0 bytes
modules/h2/src/docsrc/images/h2-logo-2.png | Bin 6617 -> 0 bytes
modules/h2/src/docsrc/images/h2-logo.png | Bin 12780 -> 0 bytes
modules/h2/src/docsrc/images/h2-logo.svg | 61 -
modules/h2/src/docsrc/images/h2_v2_3_7.svg | 61 -
modules/h2/src/docsrc/images/paypal-donate.png | Bin 6172 -> 0 bytes
modules/h2/src/docsrc/images/screenshot.png | Bin 113875 -> 0 bytes
modules/h2/src/docsrc/index.html | 44 -
modules/h2/src/docsrc/javadoc/animate.js | 51 -
modules/h2/src/docsrc/javadoc/classes.html | 98 -
modules/h2/src/docsrc/javadoc/index.html | 24 -
modules/h2/src/docsrc/javadoc/overview.html | 38 -
modules/h2/src/docsrc/javadoc/stylesheet.css | 171 -
modules/h2/src/docsrc/text/_docs_ja.utf8.txt | 12512 -------------------
modules/h2/src/test/tools/WEB-INF/console.html | 15 -
modules/h2/src/test/tools/WEB-INF/web.xml | 67 -
modules/h2/src/test/tools/org/h2/build/Build.java | 1192 --
.../test/tools/org/h2/build/code/AbbaDetect.java | 101 -
.../test/tools/org/h2/build/code/CheckJavadoc.java | 130 -
.../tools/org/h2/build/code/CheckTextFiles.java | 313 -
.../src/test/tools/org/h2/build/code/package.html | 14 -
.../test/tools/org/h2/build/doc/FileConverter.java | 65 -
.../test/tools/org/h2/build/doc/GenerateDoc.java | 298 -
.../test/tools/org/h2/build/doc/LinkChecker.java | 276 -
.../src/test/tools/org/h2/build/doc/MergeDocs.java | 130 -
.../tools/org/h2/build/doc/RailroadImages.java | 130 -
.../test/tools/org/h2/build/doc/SpellChecker.java | 305 -
.../test/tools/org/h2/build/doc/UploadBuild.java | 261 -
.../src/test/tools/org/h2/build/doc/WebSite.java | 168 -
.../test/tools/org/h2/build/doc/XMLChecker.java | 149 -
.../src/test/tools/org/h2/build/doc/XMLParser.java | 511 -
.../src/test/tools/org/h2/build/doc/dictionary.txt | 813 --
.../src/test/tools/org/h2/build/doclet/Doclet.java | 590 -
.../tools/org/h2/build/doclet/ResourceDoclet.java | 132 -
.../test/tools/org/h2/build/doclet/package.html | 14 -
.../org/h2/build/i18n/PrepareTranslation.java | 542 -
.../tools/org/h2/build/i18n/PropertiesToUTF8.java | 158 -
.../src/test/tools/org/h2/build/i18n/package.html | 14 -
.../tools/org/h2/build/indexer/HtmlConverter.java | 190 -
.../test/tools/org/h2/build/indexer/Indexer.java | 369 -
.../src/test/tools/org/h2/build/indexer/Page.java | 49 -
.../test/tools/org/h2/build/indexer/Weight.java | 43 -
.../src/test/tools/org/h2/build/indexer/Word.java | 82 -
.../test/tools/org/h2/build/indexer/package.html | 14 -
.../h2/src/test/tools/org/h2/jcr/Railroads.java | 129 -
modules/h2/src/test/tools/org/h2/jcr/help.csv | 99 -
modules/h2/src/test/tools/org/h2/jcr/jcr-sql2.html | 72 -
modules/h2/src/test/tools/org/h2/jcr/package.html | 14 -
.../h2/src/test/tools/org/h2/jcr/stylesheet.css | 340 -
131 files changed, 36911 deletions(-)
diff --git a/modules/h2/pom.xml b/modules/h2/pom.xml
index 5ba7a15..903e454 100644
--- a/modules/h2/pom.xml
+++ b/modules/h2/pom.xml
@@ -80,12 +80,6 @@
<version>${slf4j16.version}</version>
<scope>test</scope>
</dependency>
- <!-- <dependency>
- <groupId>org.postgresql</groupId>
- <artifactId>postgresql</artifactId>
- <version>42.2.5.jre7</version>
- <scope>test</scope>
- </dependency>-->
<dependency>
<groupId>org.ow2.asm</groupId>
<artifactId>asm</artifactId>
@@ -124,7 +118,6 @@
<include>**/*.js</include>
<include>org/h2/res/help.csv</include>
<include>org/h2/res/javadoc.properties</include>
- <include>org/h2/server/pg/pg_catalog.sql</include>
<include>META-INF/**</include>
</includes>
</resource>
diff --git a/modules/h2/src/docsrc/html/advanced.html b/modules/h2/src/docsrc/html/advanced.html
deleted file mode 100644
index c1d0501..0000000
--- a/modules/h2/src/docsrc/html/advanced.html
+++ /dev/null
@@ -1,1968 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Advanced
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Advanced</h1>
-<a href="#result_sets">
- Result Sets</a><br />
-<a href="#large_objects">
- Large Objects</a><br />
-<a href="#linked_tables">
- Linked Tables</a><br />
-<a href="#spatial_features">
- Spatial Features</a><br />
-<a href="#recursive_queries">
- Recursive Queries</a><br />
-<a href="#updatable_views">
- Updatable Views</a><br />
-<a href="#transaction_isolation">
- Transaction Isolation</a><br />
-<a href="#mvcc">
- Multi-Version Concurrency Control (MVCC)</a><br />
-<a href="#clustering">
- Clustering / High Availability</a><br />
-<a href="#two_phase_commit">
- Two Phase Commit</a><br />
-<a href="#compatibility">
- Compatibility</a><br />
-<a href="#keywords">
- Keywords / Reserved Words</a><br />
-<a href="#standards_compliance">
- Standards Compliance</a><br />
-<a href="#windows_service">
- Run as Windows Service</a><br />
-<a href="#odbc_driver">
- ODBC Driver</a><br />
-<a href="#microsoft_dot_net">
- Using H2 in Microsoft .NET</a><br />
-<a href="#acid">
- ACID</a><br />
-<a href="#durability_problems">
- Durability Problems</a><br />
-<a href="#using_recover_tool">
- Using the Recover Tool</a><br />
-<a href="#file_locking_protocols">
- File Locking Protocols</a><br />
-<a href="#passwords">
- Using Passwords</a><br />
-<a href="#password_hash">
- Password Hash</a><br />
-<a href="#sql_injection">
- Protection against SQL Injection</a><br />
-<a href="#remote_access">
- Protection against Remote Access</a><br />
-<a href="#restricting_classes">
- Restricting Class Loading and Usage</a><br />
-<a href="#security_protocols">
- Security Protocols</a><br />
-<a href="#tls_connections">
- TLS Connections</a><br />
-<a href="#uuid">
- Universally Unique Identifiers (UUID)</a><br />
-<a href="#system_properties">
- Settings Read from System Properties</a><br />
-<a href="#server_bind_address">
- Setting the Server Bind Address</a><br />
-<a href="#file_system">
- Pluggable File System</a><br />
-<a href="#file_system_split">
- Split File System</a><br />
-<a href="#database_upgrade">
- Database Upgrade</a><br />
-<a href="#java_objects_serialization">
- Java Objects Serialization</a><br />
-<a href="#custom_data_types_handler_api">
- Custom Data Types Handler API</a><br />
-<a href="#limits_limitations">
- Limits and Limitations</a><br />
-<a href="#glossary_links">
- Glossary and Links</a><br />
-
-<h2 id="result_sets">Result Sets</h2>
-
-<h3>Statements that Return a Result Set</h3>
-<p>
-The following statements return a result set: <code>SELECT, EXPLAIN, CALL, SCRIPT, SHOW, HELP</code>.
-All other statements return an update count.
-</p>
-
-<h3>Limiting the Number of Rows</h3>
-<p>
-Before the result is returned to the application, all rows are read by the database.
-Server side cursors are not supported currently.
-If only the first few rows are interesting for the application, then the
-result set size should be limited to improve the performance.
-This can be done using <code>FETCH</code> in a query
-(example: <code>SELECT * FROM TEST FETCH FIRST 100 ROWS ONLY</code>),
-or by using <code>Statement.setMaxRows(max)</code>.
-</p>
-
-<h3>Large Result Sets and External Sorting</h3>
-<p>
-For large result set, the result is buffered to disk. The threshold can be defined using the statement
-<code>SET MAX_MEMORY_ROWS</code>.
-If <code>ORDER BY</code> is used, the sorting is done using an
-external sort algorithm.
-In this case, each block of rows is sorted using quick sort, then written to disk;
-when reading the data, the blocks are merged together.
-</p>
-
-<h2 id="large_objects">Large Objects</h2>
-
-<h3>Storing and Reading Large Objects</h3>
-<p>
-If it is possible that the objects don't fit into memory, then the data type
-CLOB (for textual data) or BLOB (for binary data) should be used.
-For these data types, the objects are not fully read into memory, by using streams.
-To store a BLOB, use <code>PreparedStatement.setBinaryStream</code>. To store a CLOB, use
-<code>PreparedStatement.setCharacterStream</code>. To read a BLOB, use <code>ResultSet.getBinaryStream</code>,
-and to read a CLOB, use <code>ResultSet.getCharacterStream</code>.
-When using the client/server mode, large BLOB and CLOB data is stored in a temporary file
-on the client side.
-</p>
-
-<h3>When to use CLOB/BLOB</h3>
-<p>
-By default, this database stores large LOB (CLOB and BLOB) objects separate from the main table data.
-Small LOB objects are stored in-place, the threshold can be set using
-<a href="commands.html#set_max_length_inplace_lob" class="notranslate" >MAX_LENGTH_INPLACE_LOB</a>,
-but there is still an overhead to use CLOB/BLOB. Because of this, BLOB and CLOB
-should never be used for columns with a maximum size below about 200 bytes.
-The best threshold depends on the use case; reading in-place objects is faster
-than reading from separate files, but slows down the performance of operations
-that don't involve this column.
-</p>
-
-<h3>Large Object Compression</h3>
-<p>
-The following feature is only available for the PageStore storage engine.
-For the MVStore engine (the default for H2 version 1.4.x),
-append <code>;COMPRESS=TRUE</code> to the database URL instead.
-CLOB and BLOB values can be compressed by using
-<a href="commands.html#set_compress_lob" class="notranslate" >SET COMPRESS_LOB</a>.
-The LZF algorithm is faster but needs more disk space. By default compression is disabled, which usually speeds up write
-operations. If you store many large compressible values such as XML, HTML, text, and uncompressed binary files,
-then compressing can save a lot of disk space (sometimes more than 50%), and read operations may even be faster.
-</p>
-
-<h2 id="linked_tables">Linked Tables</h2>
-<p>
-This database supports linked tables, which means tables that don't exist in the current database but
-are just links to another database. To create such a link, use the
-<code>CREATE LINKED TABLE</code> statement:
-</p>
-<pre>
-CREATE LINKED TABLE LINK('org.postgresql.Driver', 'jdbc:postgresql:test', 'sa', 'sa', 'TEST');
-</pre>
-<p>
-You can then access the table in the usual way.
-Whenever the linked table is accessed, the database issues specific queries over JDBC.
-Using the example above, if you issue the query <code>SELECT * FROM LINK WHERE ID=1</code>,
-then the following query is run against the PostgreSQL database: <code>SELECT * FROM TEST WHERE ID=?</code>.
-The same happens for insert and update statements.
-Only simple statements are executed against the target database, that means no joins
-(queries that contain joins are converted to simple queries).
-Prepared statements are used where possible.
-</p>
-<p>
-To view the statements that are executed against the target table, set the trace level to 3.
-</p>
-<p>
-If multiple linked tables point to the same database (using the same database URL), the connection
-is shared. To disable this, set the system property <code>h2.shareLinkedConnections=false</code>.
-</p>
-<p>
-The statement <a href="commands.html#create_linked_table" class="notranslate" >CREATE LINKED TABLE</a>
-supports an optional schema name parameter.
-</p>
-<p>
-The following are not supported because they may result in a deadlock:
-creating a linked table to the same database,
-and creating a linked table to another database using the server mode if the other database is open in the same server
-(use the embedded mode instead).
-</p>
-<p>
-Data types that are not supported in H2 are also not supported for linked tables,
-for example unsigned data types if the value is outside the range of the signed type.
-In such cases, the columns needs to be cast to a supported type.
-</p>
-
-<h2 id="updatable_views">Updatable Views</h2>
-<p>
-By default, views are not updatable.
-To make a view updatable, use an "instead of" trigger as follows:
-</p>
-<pre>
-CREATE TRIGGER TRIGGER_NAME
-INSTEAD OF INSERT, UPDATE, DELETE
-ON VIEW_NAME
-FOR EACH ROW CALL "com.acme.TriggerClassName";
-</pre>
-<p>
-Update the base table(s) within the trigger as required.
-For details, see the sample application <code>org.h2.samples.UpdatableView</code>.
-</p>
-
-<h2 id="transaction_isolation">Transaction Isolation</h2>
-<p>
-Please note that most data definition language (DDL) statements,
-such as "create table", commit the current transaction.
-See the <a href="commands.html">Commands</a> for details.
-</p>
-<p>
-Transaction isolation is provided for all data manipulation language (DML) statements.
-</p>
-<p>
-Please note that with default MVStore storage engine table level locking is not used.
-Instead, rows are locked for update, and read committed is used in all cases
-except for explicitly selected read uncommitted transaction isolation level.
-</p>
-<p>
-This database supports the following transaction isolation levels:
-</p>
-<ul>
-<li><b>Read Committed</b><br />
- This is the default level.
- Read locks are released immediately after executing the statement, but write locks are kept until the transaction commits.
- Higher concurrency is possible when using this level.<br />
- To enable, execute the SQL statement <code>SET LOCK_MODE 3</code><br />
- or append <code>;LOCK_MODE=3</code> to the database URL: <code>jdbc:h2:~/test;LOCK_MODE=3</code>
-</li><li>
-<b>Serializable</b><br />
- Both read locks and write locks are kept until the transaction commits.
- To enable, execute the SQL statement <code>SET LOCK_MODE 1</code><br />
- or append <code>;LOCK_MODE=1</code> to the database URL: <code>jdbc:h2:~/test;LOCK_MODE=1</code>
-</li><li><b>Read Uncommitted</b><br />
- This level means that transaction isolation is disabled.
- This level is not supported by PageStore engine if multi-threaded mode is enabled.
- <br />
- To enable, execute the SQL statement <code>SET LOCK_MODE 0</code><br />
- or append <code>;LOCK_MODE=0</code> to the database URL: <code>jdbc:h2:~/test;LOCK_MODE=0</code>
-</li>
-</ul>
-<p>
-When using the isolation level 'serializable', dirty reads, non-repeatable reads, and phantom reads are prohibited.
-</p>
-<ul>
-<li><b>Dirty Reads</b><br />
- Means a connection can read uncommitted changes made by another connection.<br />
- Possible with: read uncommitted
-</li><li><b>Non-Repeatable Reads</b><br />
- A connection reads a row, another connection changes a row and commits,
- and the first connection re-reads the same row and gets the new result.<br />
- Possible with: read uncommitted, read committed
-</li><li><b>Phantom Reads</b><br />
- A connection reads a set of rows using a condition, another connection
- inserts a row that falls in this condition and commits, then the first connection
- re-reads using the same condition and gets the new row.<br />
- Possible with: read uncommitted, read committed
-</li>
-</ul>
-
-<h3 id="mvcc">Multi-Version Concurrency Control (MVCC)</h3>
-<p>
-With default MVStore engine delete, insert and update operations only issue a shared lock on the table.
-An exclusive lock is still used when adding or removing columns or when dropping the table.
-Connections only 'see' committed data, and own changes. That means, if connection A updates
-a row but doesn't commit this change yet, connection B will see the old value.
-Only when the change is committed, the new value is visible by other connections
-(read committed). If multiple connections concurrently try to lock or update the same row, the
-database waits until it can apply the change, but at most until the lock timeout expires.
-</p>
-
-<h3>Table Level Locking (PageStore engine)</h3>
-<p>
-With PageStore engine to make sure all connections only see consistent data, table level locking is used.
-This mechanism does not allow high concurrency, but is very fast.
-Shared locks and exclusive locks are supported.
-Before reading from a table, the database tries to add a shared lock to the table
-(this is only possible if there is no exclusive lock on the object by another connection).
-If the shared lock is added successfully, the table can be read. It is allowed that
-other connections also have a shared lock on the same object. If a connection wants
-to write to a table (update or delete a row), an exclusive lock is required. To get the
-exclusive lock, other connection must not have any locks on the object. After the
-connection commits, all locks are released.
-This database keeps all locks in memory.
-When a lock is released, and multiple connections are waiting for it, one of them is picked at random.
-</p>
-
-<h3>Lock Timeout</h3>
-<p>
-If a connection cannot get a lock on an object, the connection waits for some amount
-of time (the lock timeout). During this time, hopefully the connection holding the
-lock commits and it is then possible to get the lock. If this is not possible because
-the other connection does not release the lock for some time, the unsuccessful
-connection will get a lock timeout exception. The lock timeout can be set individually
-for each connection.
-</p>
-
-<h2 id="clustering">Clustering / High Availability</h2>
-<p>
-This database supports a simple clustering / high availability mechanism. The architecture is:
-two database servers run on two different computers, and on both computers is a copy of the
-same database. If both servers run, each database operation is executed on both computers.
-If one server fails (power, hardware or network failure), the other server can still continue to work.
-From this point on, the operations will be executed only on one server until the other server
-is back up.
-</p><p>
-Clustering can only be used in the server mode (the embedded mode does not support clustering).
-The cluster can be re-created using the <code>CreateCluster</code> tool without stopping
-the remaining server. Applications that are still connected are automatically disconnected,
-however when appending <code>;AUTO_RECONNECT=TRUE</code>, they will recover from that.
-</p><p>
-To initialize the cluster, use the following steps:
-</p>
-<ul>
-<li>Create a database
-</li><li>Use the <code>CreateCluster</code> tool to copy the database to
- another location and initialize the clustering.
- Afterwards, you have two databases containing the same data.
-</li><li>Start two servers (one for each copy of the database)
-</li><li>You are now ready to connect to the databases with the client application(s)
-</li></ul>
-
-<h3>Using the CreateCluster Tool</h3>
-<p>
-To understand how clustering works, please try out the following example.
-In this example, the two databases reside on the same computer, but usually, the
-databases will be on different servers.
-</p>
-<ul>
-<li>Create two directories: <code>server1, server2</code>.
- Each directory will simulate a directory on a computer.
-</li><li>Start a TCP server pointing to the first directory.
- You can do this using the command line:
-<pre>
-java org.h2.tools.Server
- -tcp -tcpPort 9101
- -baseDir server1
-</pre>
-</li><li>Start a second TCP server pointing to the second directory.
- This will simulate a server running on a second (redundant) computer.
- You can do this using the command line:
-<pre>
-java org.h2.tools.Server
- -tcp -tcpPort 9102
- -baseDir server2
-</pre>
-</li><li>Use the <code>CreateCluster</code> tool to initialize clustering.
- This will automatically create a new, empty database if it does not exist.
- Run the tool on the command line:
-<pre>
-java org.h2.tools.CreateCluster
- -urlSource jdbc:h2:tcp://localhost:9101/~/test
- -urlTarget jdbc:h2:tcp://localhost:9102/~/test
- -user sa
- -serverList localhost:9101,localhost:9102
-</pre>
-</li><li>You can now connect to the databases using
-an application or the H2 Console using the JDBC URL
-<code>jdbc:h2:tcp://localhost:9101,localhost:9102/~/test</code>
-</li><li>If you stop a server (by killing the process),
-you will notice that the other machine continues to work,
-and therefore the database is still accessible.
-</li><li>To restore the cluster, you first need to delete the
-database that failed, then restart the server that was stopped,
-and re-run the <code>CreateCluster</code> tool.
-</li></ul>
-
-<h3>Detect Which Cluster Instances are Running</h3>
-<p>
-To find out which cluster nodes are currently running, execute the following SQL statement:
-</p>
-<pre>
-SELECT VALUE FROM INFORMATION_SCHEMA.SETTINGS WHERE NAME='CLUSTER'
-</pre>
-<p>
-If the result is <code>''</code> (two single quotes), then the cluster mode is disabled. Otherwise, the list of
-servers is returned, enclosed in single quote. Example: <code>'server1:9191,server2:9191'</code>.
-</p>
-
-<p>
-It is also possible to get the list of servers by using Connection.getClientInfo().
-</p>
-
-<p>
-The property list returned from <code>getClientInfo()</code> contains a <code>numServers</code> property that returns the
-number of servers that are in the connection list. To get the actual servers, <code>getClientInfo()</code> also has
-properties <code>server0</code>..<code>serverX</code>, where serverX is the number of servers minus 1.
-</p>
-
-<p>
-Example: To get the 2nd server in the connection list one uses <code>getClientInfo('server1')</code>.
-<b>Note:</b> The <code>serverX</code> property only returns IP addresses and ports and not hostnames.
-</p>
-
-<h3>Clustering Algorithm and Limitations</h3>
-<p>
-Read-only queries are only executed against the first cluster node, but all other statements are
-executed against all nodes. There is currently no load balancing made to avoid problems with
-transactions. The following functions may yield different results on different cluster nodes and must be
-executed with care: <code>UUID(), RANDOM_UUID(), SECURE_RAND(), SESSION_ID(),
-MEMORY_FREE(), MEMORY_USED(), CSVREAD(), CSVWRITE(), RAND()</code> [when not using a seed].
-Those functions should not be used directly in modifying statements
-(for example <code>INSERT, UPDATE, MERGE</code>). However, they can be used
-in read-only statements and the result can then be used for modifying statements.
-Using auto-increment and identity columns is currently not supported.
-Instead, sequence values need to be manually requested and then used to insert data (using two statements).
-</p>
-<p>
-When using the cluster modes, result sets are read fully in memory by the client, so that
-there is no problem if the server dies that executed the query. Result sets must fit in memory
-on the client side.
-</p>
-<p>
-The SQL statement <code>SET AUTOCOMMIT FALSE</code> is not supported in the cluster mode.
-To disable autocommit, the method <code>Connection.setAutoCommit(false)</code> needs to be called.
-</p>
-<p>
-It is possible that a transaction from one connection overtakes a transaction from a different connection.
-Depending on the operations, this might result in different results, for example when
-conditionally incrementing a value in a row.
-</p>
-
-<h2 id="two_phase_commit">Two Phase Commit</h2>
-<p>
-The two phase commit protocol is supported. 2-phase-commit works as follows:
-</p>
-<ul>
-<li>Autocommit needs to be switched off
-</li><li>A transaction is started, for example by inserting a row
-</li><li>The transaction is marked 'prepared' by executing the SQL statement
- <code>PREPARE COMMIT transactionName</code>
-</li><li>The transaction can now be committed or rolled back
-</li><li>If a problem occurs before the transaction was successfully committed or rolled back
- (for example because a network problem occurred), the transaction is in the state 'in-doubt'
-</li><li>When re-connecting to the database, the in-doubt transactions can be listed
- with <code>SELECT * FROM INFORMATION_SCHEMA.IN_DOUBT</code>
-</li><li>Each transaction in this list must now be committed or rolled back by executing
- <code>COMMIT TRANSACTION transactionName</code> or
- <code>ROLLBACK TRANSACTION transactionName</code>
-</li><li>The database needs to be closed and re-opened to apply the changes
-</li></ul>
-
-<h2 id="compatibility">Compatibility</h2>
-<p>
-This database is (up to a certain point) compatible to other databases such as HSQLDB, MySQL and PostgreSQL.
-There are certain areas where H2 is incompatible.
-</p>
-
-<h3>Transaction Commit when Autocommit is On</h3>
-<p>
-At this time, this database engine commits a transaction (if autocommit is switched on) just before returning the result.
-For a query, this means the transaction is committed even before the application scans through the result set, and before the result set is closed.
-Other database engines may commit the transaction in this case when the result set is closed.
-</p>
-
-<h2 id="keywords">Keywords / Reserved Words</h2>
-<p>
-There is a list of keywords that can't be used as identifiers (table names, column names and so on),
-unless they are quoted (surrounded with double quotes).
-The following tokens are keywords in H2:
-</p>
-<table class="main">
-<thead>
-<tr>
-<th>Keyword</th>
-<th>H2</th>
-<th>SQL:​2011</th>
-<th>SQL:​2008</th>
-<th>SQL:​2003</th>
-<th>SQL:​1999</th>
-<th>SQL-92</th>
-</tr>
-</thead>
-<tbody>
-<tr><td>ALL</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>AND</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>ARRAY</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td></td></tr>
-<tr><td>AS</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>BETWEEN</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>NR</td><td>+</td></tr>
-<tr><td>BOTH</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CASE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CHECK</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CONSTRAINT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CROSS</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CURRENT_DATE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CURRENT_TIME</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CURRENT_TIMESTAMP</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>CURRENT_USER</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>DISTINCT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>EXCEPT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>EXISTS</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>NR</td><td>+</td></tr>
-<tr><td>FALSE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>FETCH</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>FILTER</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td></td><td></td></tr>
-<tr><td>FOR</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>FOREIGN</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>FROM</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>FULL</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>GROUP</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>GROUPS</td>
-<td>CS</td><td>+</td><td></td><td></td><td></td><td></td></tr>
-<tr><td>HAVING</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>IF</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>ILIKE</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>IN</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>INNER</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>INTERSECT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>INTERSECTS</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>INTERVAL</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>IS</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>JOIN</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>LEADING</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>LEFT</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>LIKE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>LIMIT</td>
-<td>+</td><td></td><td></td><td></td><td>+</td><td></td></tr>
-<tr><td>LOCALTIME</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td></td></tr>
-<tr><td>LOCALTIMESTAMP</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td></td></tr>
-<tr><td>MINUS</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>NATURAL</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>NOT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>NULL</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>OFFSET</td>
-<td>+</td><td>+</td><td>+</td><td></td><td></td><td></td></tr>
-<tr><td>ON</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>OR</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>ORDER</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>OVER</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td></td><td></td></tr>
-<tr><td>PARTITION</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td></td><td></td></tr>
-<tr><td>PRIMARY</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>QUALIFY</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>RANGE</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td></td><td></td></tr>
-<tr><td>REGEXP</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>RIGHT</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>ROW</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td></td></tr>
-<tr><td>_ROWID_</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>ROWNUM</td>
-<td>+</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>ROWS</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>SELECT</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>SYSDATE</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>SYSTIME</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>SYSTIMESTAMP</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>TABLE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>TODAY</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>TOP</td>
-<td>CS</td><td></td><td></td><td></td><td></td><td></td></tr>
-<tr><td>TRAILING</td>
-<td>CS</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>TRUE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>UNION</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>UNIQUE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>VALUES</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>WHERE</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-<tr><td>WINDOW</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td></td><td></td></tr>
-<tr><td>WITH</td>
-<td>+</td><td>+</td><td>+</td><td>+</td><td>+</td><td>+</td></tr>
-</tbody>
-</table>
-<p>
-Some keywords in H2 are context-sensitive (CS), such keywords may be used as identifiers in some places,
-but cannot be used as identifiers in others.
-Most keywords in H2 are also reserved (+) or non-reserved (NR) words in the SQL Standard.
-Newer versions of H2 may have more keywords than older ones.
-</p>
-
-<h2 id="standards_compliance">Standards Compliance</h2>
-<p>
-This database tries to be as much standard compliant as possible. For the SQL language, ANSI/ISO is the main
-standard. There are several versions that refer to the release date: SQL-92, SQL:1999, and SQL:2003.
-Unfortunately, the standard documentation is not freely available. Another problem is that important features
-are not standardized. Whenever this is the case, this database tries to be compatible to other databases.
-</p>
-
-<h3>Supported Character Sets, Character Encoding, and Unicode</h3>
-<p>
-H2 internally uses Unicode, and supports all character encoding systems and character sets supported by the virtual machine you use.
-</p>
-
-<h2 id="windows_service">Run as Windows Service</h2>
-<p>
-Using a native wrapper / adapter, Java applications can be run as a Windows Service.
-There are various tools available to do that. The Java Service Wrapper from
-<a href="https://wrapper.tanukisoftware.org">Tanuki Software, Inc.</a>
-is included in the installation. Batch files are provided to install, start, stop and uninstall the
-H2 Database Engine Service. This service contains the TCP Server and the H2 Console web application.
-The batch files are located in the directory <code>h2/service</code>.
-</p>
-<p>
-The service wrapper bundled with H2 is a 32-bit version.
-To use a 64-bit version of Windows (x64), you need to use a 64-bit version of the wrapper,
-for example the one from
-<a href="https://www.krenger.ch/blog/java-service-wrapper-3-5-14-for-windows-x64/">
-Simon Krenger</a>.
-</p>
-<p>
-When running the database as a service, absolute path should be used.
-Using <code>~</code> in the database URL is problematic in this case,
-because it means to use the home directory of the current user.
-The service might run without or with the wrong user, so that
-the database files might end up in an unexpected place.
-</p>
-
-<h3>Install the Service</h3>
-<p>
-The service needs to be registered as a Windows Service first.
-To do that, double click on <code>1_install_service.bat</code>.
-If successful, a command prompt window will pop up and disappear immediately. If not, a message will appear.
-</p>
-
-<h3>Start the Service</h3>
-<p>
-You can start the H2 Database Engine Service using the service manager of Windows,
-or by double clicking on <code>2_start_service.bat</code>.
-Please note that the batch file does not print an error message if the service is not installed.
-</p>
-
-<h3>Connect to the H2 Console</h3>
-<p>
-After installing and starting the service, you can connect to the H2 Console application using a browser.
-Double clicking on <code>3_start_browser.bat</code> to do that. The
-default port (8082) is hard coded in the batch file.
-</p>
-
-<h3>Stop the Service</h3>
-<p>
-To stop the service, double click on <code>4_stop_service.bat</code>.
-Please note that the batch file does not print an error message if the service is not installed or started.
-</p>
-
-<h3>Uninstall the Service</h3>
-<p>
-To uninstall the service, double click on <code>5_uninstall_service.bat</code>.
-If successful, a command prompt window will pop up and disappear immediately. If not, a message will appear.
-</p>
-
-<h3>Additional JDBC drivers</h3>
-<p>
-To use other databases (for example MySQL), the location of the JDBC drivers of those databases need to be
-added to the environment variables <code>H2DRIVERS</code> or <code>CLASSPATH</code> before
-installing the service. Multiple drivers can be set; each entry needs to be separated with a <code>;</code>
-(Windows) or <code>:</code> (other operating systems). Spaces in the path names are supported.
-The settings must not be quoted.
-</p>
-
-<h2 id="odbc_driver">ODBC Driver</h2>
-<p>
-This database does not come with its own ODBC driver at this time,
-but it supports the PostgreSQL network protocol.
-Therefore, the PostgreSQL ODBC driver can be used.
-Support for the PostgreSQL network protocol is quite new and should be viewed
-as experimental. It should not be used for production applications.
-</p>
-<p>
-To use the PostgreSQL ODBC driver on 64 bit versions of Windows,
-first run <code>c:/windows/syswow64/odbcad32.exe</code>.
-At this point you set up your DSN just like you would on any other system.
-See also:
-<a href="https://www.postgresql.org/message-id/dg76q0$khn$1@sea.gmane.org">Re: ODBC Driver on Windows 64 bit</a>
-</p>
-
-<h3>ODBC Installation</h3>
-<p>
-First, the ODBC driver must be installed.
-Any recent PostgreSQL ODBC driver should work, however version 8.2 (<code>psqlodbc-08_02*</code>) or newer is recommended.
-The Windows version of the PostgreSQL ODBC driver is available at
-<a href="https://www.postgresql.org/ftp/odbc/versions/msi/">https://www.postgresql.org/ftp/odbc/versions/msi/</a>.
-</p>
-
-<h3>Starting the Server</h3>
-<p>
-After installing the ODBC driver, start the H2 Server using the command line:
-</p>
-<pre>
-java -cp h2*.jar org.h2.tools.Server
-</pre>
-<p>
-The PG Server (PG for PostgreSQL protocol) is started as well.
-By default, databases are stored in the current working directory where the server is started.
-Use <code>-baseDir</code> to save databases in another directory, for example the user home directory:
-</p>
-<pre>
-java -cp h2*.jar org.h2.tools.Server -baseDir ~
-</pre>
-<p>
-The PG server can be started and stopped from within a Java application as follows:
-</p>
-<pre>
-Server server = Server.createPgServer("-baseDir", "~");
-server.start();
-...
-server.stop();
-</pre>
-<p>
-By default, only connections from localhost are allowed. To allow remote connections, use
-<code>-pgAllowOthers</code> when starting the server.
-</p>
-<p>
-To map an ODBC database name to a different JDBC database name,
-use the option <code>-key</code> when starting the server.
-Please note only one mapping is allowed. The following will map the ODBC database named
-<code>TEST</code> to the database URL <code>jdbc:h2:~/data/test;cipher=aes</code>:
-</p>
-<pre>
-java org.h2.tools.Server -pg -key TEST "~/data/test;cipher=aes"
-</pre>
-
-<h3>ODBC Configuration</h3>
-<p>
-After installing the driver, a new Data Source must be added. In Windows,
-run <code>odbcad32.exe</code> to open the Data Source Administrator. Then click on 'Add...'
-and select the PostgreSQL Unicode driver. Then click 'Finish'.
-You will be able to change the connection properties.
-The property column represents the property key in the <code>odbc.ini</code> file
-(which may be different from the GUI).
-</p>
-<table class="main">
-<tr><th>Property</th><th>Example</th><th>Remarks</th></tr>
-<tr><td>Data Source</td><td>H2 Test</td><td>The name of the ODBC Data Source</td></tr>
-<tr><td>Database</td><td>~/test;ifexists=true</td>
- <td>
- The database name. This can include connections settings.
- By default, the database is stored in the current working directory
- where the Server is started except when the -baseDir setting is used.
- The name must be at least 3 characters.
- </td></tr>
-<tr><td>Servername</td><td>localhost</td><td>The server name or IP address.<br />By default, only remote connections are allowed</td></tr>
-<tr><td>Username</td><td>sa</td><td>The database user name.</td></tr>
-<tr><td>SSL</td><td>false (disabled)</td><td>At this time, SSL is not supported.</td></tr>
-<tr><td>Port</td><td>5435</td><td>The port where the PG Server is listening.</td></tr>
-<tr><td>Password</td><td>sa</td><td>The database password.</td></tr>
-</table>
-<p>
-To improve performance, please enable 'server side prepare' under Options / Datasource / Page 2 / Server side prepare.
-</p>
-<p>
-Afterwards, you may use this data source.
-</p>
-
-<h3>PG Protocol Support Limitations</h3>
-<p>
-At this time, only a subset of the PostgreSQL network protocol is implemented.
-Also, there may be compatibility problems on the SQL level, with the catalog, or with text encoding.
-Problems are fixed as they are found.
-Currently, statements can not be canceled when using the PG protocol.
-Also, H2 does not provide index meta over ODBC.
-</p>
-<p>
-PostgreSQL ODBC Driver Setup requires a database password; that means it
-is not possible to connect to H2 databases without password. This is a limitation
-of the ODBC driver.
-</p>
-
-<h3>Security Considerations</h3>
-<p>
-Currently, the PG Server does not support challenge response or encrypt passwords.
-This may be a problem if an attacker can listen to the data transferred between the ODBC driver
-and the server, because the password is readable to the attacker.
-Also, it is currently not possible to use encrypted SSL connections.
-Therefore the ODBC driver should not be used where security is important.
-</p>
-<p>
-The first connection that opens a database using the PostgreSQL server needs to be an administrator user.
-Subsequent connections don't need to be opened by an administrator.
-</p>
-
-<h3>Using Microsoft Access</h3>
-<p>
-When using Microsoft Access to edit data in a linked H2 table, you may need to enable the following option:
-Tools - Options - Edit/Find - ODBC fields.
-</p>
-
-<h2 id="microsoft_dot_net">Using H2 in Microsoft .NET</h2>
-<p>
-The database can be used from Microsoft .NET even without using Java, by using IKVM.NET.
-You can access a H2 database on .NET using the JDBC API, or using the ADO.NET interface.
-</p>
-
-<h3>Using the ADO.NET API on .NET</h3>
-<p>
-An implementation of the ADO.NET interface is available in the open source project
-<a href="https://code.google.com/archive/p/h2sharp/">H2Sharp</a>.
-</p>
-
-<h3>Using the JDBC API on .NET</h3>
-<ul><li>Install the .NET Framework from <a href="https://www.microsoft.com">Microsoft</a>.
- Mono has not yet been tested.
-</li><li>Install <a href="http://www.ikvm.net">IKVM.NET</a>.
-</li><li>Copy the <code>h2*.jar</code> file to <code>ikvm/bin</code>
-</li><li>Run the H2 Console using:
- <code>ikvm -jar h2*.jar</code>
-</li><li>Convert the H2 Console to an <code>.exe</code> file using:
- <code>ikvmc -target:winexe h2*.jar</code>.
- You may ignore the warnings.
-</li><li>Create a <code>.dll</code> file using (change the version accordingly):
- <code>ikvmc.exe -target:library -version:1.0.69.0 h2*.jar</code>
-</li></ul>
-<p>
-If you want your C# application use H2, you need to add the <code>h2.dll</code> and the
-<code>IKVM.OpenJDK.ClassLibrary.dll</code> to your C# solution. Here some sample code:
-</p>
-<pre>
-using System;
-using java.sql;
-
-class Test
-{
- static public void Main()
- {
- org.h2.Driver.load();
- Connection conn = DriverManager.getConnection("jdbc:h2:~/test", "sa", "sa");
- Statement stat = conn.createStatement();
- ResultSet rs = stat.executeQuery("SELECT 'Hello World'");
- while (rs.next())
- {
- Console.WriteLine(rs.getString(1));
- }
- }
-}
-</pre>
-
-<h2 id="acid">ACID</h2>
-<p>
-In the database world, ACID stands for:
-</p>
-<ul>
-<li>Atomicity: transactions must be atomic, meaning either all tasks are performed or none.
-</li><li>Consistency: all operations must comply with the defined constraints.
-</li><li>Isolation: transactions must be isolated from each other.
-</li><li>Durability: committed transaction will not be lost.
-</li></ul>
-
-<h3>Atomicity</h3>
-<p>
-Transactions in this database are always atomic.
-</p>
-
-<h3>Consistency</h3>
-<p>
-By default, this database is always in a consistent state.
-Referential integrity rules are enforced except when
-explicitly disabled.
-</p>
-
-<h3>Isolation</h3>
-<p>
-For H2, as with most other database systems, the default isolation level is 'read committed'.
-This provides better performance, but also means that transactions are not completely isolated.
-H2 supports the transaction isolation levels 'serializable', 'read committed', and 'read uncommitted'.
-</p>
-
-<h3>Durability</h3>
-<p>
-This database does not guarantee that all committed transactions survive a power failure.
-Tests show that all databases sometimes lose transactions on power failure (for details, see below).
-Where losing transactions is not acceptable, a laptop or UPS (uninterruptible power supply) should be used.
-If durability is required for all possible cases of hardware failure, clustering should be used,
-such as the H2 clustering mode.
-</p>
-
-<h2 id="durability_problems">Durability Problems</h2>
-<p>
-Complete durability means all committed transaction survive a power failure.
-Some databases claim they can guarantee durability, but such claims are wrong.
-A durability test was run against H2, HSQLDB, PostgreSQL, and Derby.
-All of those databases sometimes lose committed transactions.
-The test is included in the H2 download, see <code>org.h2.test.poweroff.Test</code>.
-</p>
-
-<h3>Ways to (Not) Achieve Durability</h3>
-<p>
-Making sure that committed transactions are not lost is more complicated than it seems first.
-To guarantee complete durability, a database must ensure that the log record is on the hard drive
-before the commit call returns. To do that, databases use different methods. One
-is to use the 'synchronous write' file access mode. In Java, <code>RandomAccessFile</code>
-supports the modes <code>rws</code> and <code>rwd</code>:
-</p>
-<ul>
-<li><code>rwd</code>: every update to the file's content is written synchronously to the underlying storage device.
-</li><li><code>rws</code>: in addition to <code>rwd</code>, every update to the metadata is written synchronously.</li>
-</ul>
-<p>
-A test (<code>org.h2.test.poweroff.TestWrite</code>) with one of those modes achieves
-around 50 thousand write operations per second.
-Even when the operating system write buffer is disabled, the write rate is around 50 thousand operations per second.
-This feature does not force changes to disk because it does not flush all buffers.
-The test updates the same byte in the file again and again. If the hard drive was able to write at this rate,
-then the disk would need to make at least 50 thousand revolutions per second, or 3 million RPM
-(revolutions per minute). There are no such hard drives. The hard drive used for the test is about 7200 RPM,
-or about 120 revolutions per second. There is an overhead, so the maximum write rate must be lower than that.
-</p>
-<p>
-Calling <code>fsync</code> flushes the buffers. There are two ways to do that in Java:
-</p>
-<ul>
-<li><code>FileDescriptor.sync()</code>. The documentation says that this forces all system
-buffers to synchronize with the underlying device.
-This method is supposed to return after all in-memory modified copies of buffers associated with this file descriptor
-have been written to the physical medium.
-</li><li><code>FileChannel.force()</code>. This method is supposed
-to force any updates to this channel's file to be written to the storage device that contains it.
-</li></ul>
-<p>
-By default, MySQL calls <code>fsync</code> for each commit. When using one of those methods, only around 60 write operations
-per second can be achieved, which is consistent with the RPM rate of the hard drive used.
-Unfortunately, even when calling <code>FileDescriptor.sync()</code> or
-<code>FileChannel.force()</code>,
-data is not always persisted to the hard drive, because most hard drives do not obey
-<code>fsync()</code>: see
-<a href="https://hardware.slashdot.org/story/05/05/13/0529252/your-hard-drive-lies-to-you">Your Hard Drive Lies to You</a>.
-In Mac OS X, <code>fsync</code> does not flush hard drive buffers. See
-<a href="https://lists.apple.com/archives/darwin-dev/2005/Feb/msg00072.html">Bad fsync?</a>.
-So the situation is confusing, and tests prove there is a problem.
-</p>
-<p>
-Trying to flush hard drive buffers is hard, and if you do the performance is very bad.
-First you need to make sure that the hard drive actually flushes all buffers.
-Tests show that this can not be done in a reliable way.
-Then the maximum number of transactions is around 60 per second.
-Because of those reasons, the default behavior of H2 is to delay writing committed transactions.
-</p>
-<p>
-In H2, after a power failure, a bit more than one second of committed transactions may be lost.
-To change the behavior, use <code>SET WRITE_DELAY</code> and
-<code>CHECKPOINT SYNC</code>.
-Most other databases support commit delay as well.
-In the performance comparison, commit delay was used for all databases that support it.
-</p>
-
-<h3>Running the Durability Test</h3>
-<p>
-To test the durability / non-durability of this and other databases, you can use the test application
-in the package <code>org.h2.test.poweroff</code>.
-Two computers with network connection are required to run this test.
-One computer just listens, while the test application is run (and power is cut) on the other computer.
-The computer with the listener application opens a TCP/IP port and listens for an incoming connection.
-The second computer first connects to the listener, and then created the databases and starts inserting
-records. The connection is set to 'autocommit', which means after each inserted record a commit is performed
-automatically. Afterwards, the test computer notifies the listener that this record was inserted successfully.
-The listener computer displays the last inserted record number every 10 seconds. Now, switch off the power
-manually, then restart the computer, and run the application again. You will find out that in most cases,
-none of the databases contains all the records that the listener computer knows about. For details, please
-consult the source code of the listener and test application.
-</p>
-
-<h2 id="using_recover_tool">Using the Recover Tool</h2>
-<p>
-The <code>Recover</code> tool can be used to extract the contents of a database file, even if the database is corrupted.
-It also extracts the content of the transaction log and large objects (CLOB or BLOB).
-To run the tool, type on the command line:
-</p>
-<pre>
-java -cp h2*.jar org.h2.tools.Recover
-</pre>
-<p>
-For each database in the current directory, a text file will be created.
-This file contains raw insert statements (for the data) and data definition (DDL) statements to recreate
-the schema of the database. This file can be executed using the <code>RunScript</code> tool or a
-<code>RUNSCRIPT FROM</code> SQL statement. The script includes at least one
-<code>CREATE USER</code> statement. If you run the script against a database that was created with the same
-user, or if there are conflicting users, running the script will fail. Consider running the script
-against a database that was created with a user name that is not in the script.
-</p>
-<p>
-The <code>Recover</code> tool creates a SQL script from database file. It also processes the transaction log.
-</p>
-<p>
-To verify the database can recover at any time, append <code>;RECOVER_TEST=64</code>
-to the database URL in your test environment. This will simulate an application crash after each 64 writes to the database file.
-A log file named <code>databaseName.h2.db.log</code> is created that lists the operations.
-The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
-</p>
-
-<h2 id="file_locking_protocols">File Locking Protocols</h2>
-<p>
-Multiple concurrent connections to the same database are supported, however a database file
-can only be open for reading and writing (in embedded mode) by one process at the same time.
-Otherwise, the processes would overwrite each others data and corrupt the database file.
-To protect against this problem, whenever a database is opened, a lock file is created
-to signal other processes that the database is in use. If the database is closed, or if the process that opened
-the database stops normally, this lock file is deleted.
-</p><p>
-In special cases (if the process did not terminate normally, for example because
-there was a power failure), the lock file is not deleted by the process that created it.
-That means the existence of the lock file is not a safe protocol for file locking.
-However, this software uses a challenge-response protocol to protect the database
-files. There are two methods (algorithms) implemented to provide both security
-(that is, the same database files cannot be opened by two processes at the same time)
-and simplicity (that is, the lock file does not need to be deleted manually by the user).
-The two methods are 'file method' and 'socket methods'.
-</p>
-<p>
-The file locking protocols (except the file locking method 'FS')
-have the following limitation: if a shared file system is used,
-and the machine with the lock owner is sent to sleep (standby or hibernate),
-another machine may take over. If the machine that originally held the lock
-wakes up, the database may become corrupt. If this situation can occur,
-the application must ensure the database is closed when the application
-is put to sleep.
-</p>
-
-<h3>File Locking Method 'File'</h3>
-<p>
-The default method for database file locking for version 1.3 and older is the 'File Method'.
-The algorithm is:
-</p>
-<ul>
-<li>If the lock file does not exist, it is created (using the atomic operation
-<code>File.createNewFile</code>).
-Then, the process waits a little bit (20 ms) and checks the file again. If the file was changed
-during this time, the operation is aborted. This protects against a race condition
-when one process deletes the lock file just after another one create it, and a third process creates
-the file again. It does not occur if there are only two writers.
-</li><li>
-If the file can be created, a random number is inserted together with the locking method
-('file'). Afterwards, a watchdog thread is started that
-checks regularly (every second once by default) if the file was deleted or modified by
-another (challenger) thread / process. Whenever that occurs, the file is overwritten with the
-old data. The watchdog thread runs with high priority so that a change to the lock file does
-not get through undetected even if the system is very busy. However, the watchdog thread
-does use very little resources (CPU time), because it waits most of the time. Also, the watchdog only reads from the hard disk
-and does not write to it.
-</li><li>
-If the lock file exists and was recently modified, the process waits for some time (up to two seconds).
-If it was still changed, an exception is thrown (database is locked). This is done to eliminate race conditions with many concurrent
-writers. Afterwards, the file is overwritten with a new version (challenge).
-After that, the thread waits for 2 seconds.
-If there is a watchdog thread protecting the file, he will overwrite the change
-and this process will fail to lock the database.
-However, if there is no watchdog thread, the lock file will still be as written by
-this thread. In this case, the file is deleted and atomically created again.
-The watchdog thread is started in this case and the file is locked.
-</li></ul>
-<p>
-This algorithm is tested with over 100 concurrent threads. In some cases, when there are
-many concurrent threads trying to lock the database, they block each other (meaning
-the file cannot be locked by any of them) for some time. However, the file never gets
-locked by two threads at the same time. However using that many concurrent threads
-/ processes is not the common use case. Generally, an application should throw an error
-to the user if it cannot open a database, and not try again in a (fast) loop.
-</p>
-
-<h3>File Locking Method 'Socket'</h3>
-<p>
-There is a second locking mechanism implemented, but disabled by default.
-To use it, append <code>;FILE_LOCK=SOCKET</code> to the database URL.
-The algorithm is:
-</p>
-<ul>
-<li>If the lock file does not exist, it is created.
-Then a server socket is opened on a defined port, and kept open.
-The port and IP address of the process that opened the database is written
-into the lock file.
-</li><li>If the lock file exists, and the lock method is 'file', then the software switches
-to the 'file' method.
-</li><li>If the lock file exists, and the lock method is 'socket', then the process
-checks if the port is in use. If the original process is still running, the port is in use
-and this process throws an exception (database is in use). If the original process
-died (for example due to a power failure, or abnormal termination of the virtual machine),
-then the port was released. The new process deletes the lock file and starts again.
-</li></ul>
-<p>
-This method does not require a watchdog thread actively polling (reading) the same
-file every second. The problem with this method is, if the file is stored on a network
-share, two processes (running on different computers) could still open the same
-database files, if they do not have a direct TCP/IP connection.
-</p>
-
-<h3>File Locking Method 'FS'</h3>
-<p>
-This is the default mode for version 1.4 and newer.
-This database file locking mechanism uses native file system lock on the database file.
-No *.lock.db file is created in this case, and no background thread is started.
-This mechanism may not work on all systems as expected.
-Some systems allow to lock the same file multiple times within the same virtual machine,
-and on some system native file locking is not supported or files are not unlocked after a power failure.
-</p>
-<p>
-To enable this feature, append <code>;FILE_LOCK=FS</code> to the database URL.
-</p>
-<p>
-This feature is relatively new. When using it for production, please ensure
-your system does in fact lock files as expected.
-</p>
-
-<h2 id="passwords">Using Passwords</h2>
-
-<h3>Using Secure Passwords</h3>
-<p>
-Remember that weak passwords can be broken regardless of the encryption and security protocols.
-Don't use passwords that can be found in a dictionary. Appending numbers does not make passwords
-secure. A way to create good passwords that can be remembered is: take the first
-letters of a sentence, use upper and lower case characters, and creatively include special characters
-(but it's more important to use a long password than to use special characters).
-Example:
-</p><p>
-<code>i'sE2rtPiUKtT</code> from the sentence <code>it's easy to remember this password if you know the trick</code>.
-</p>
-
-<h3>Passwords: Using Char Arrays instead of Strings</h3>
-<p>
-Java strings are immutable objects and cannot be safely 'destroyed' by the application.
-After creating a string, it will remain in the main memory of the computer at least
-until it is garbage collected. The garbage collection cannot be controlled by the application,
-and even if it is garbage collected the data may still remain in memory.
-It might also be possible that the part of memory containing the password
-is swapped to disk (if not enough main memory is available), which is
-a problem if the attacker has access to the swap file of the operating system.
-</p><p>
-It is a good idea to use char arrays instead of strings for passwords.
-Char arrays can be cleared (filled with zeros) after use, and therefore the
-password will not be stored in the swap file.
-</p><p>
-This database supports using char arrays instead of string to pass user and file passwords.
-The following code can be used to do that:
-</p>
-<pre>
-import java.sql.*;
-import java.util.*;
-public class Test {
- public static void main(String[] args) throws Exception {
- String url = "jdbc:h2:~/test";
- Properties prop = new Properties();
- prop.setProperty("user", "sa");
- System.out.print("Password?");
- char[] password = System.console().readPassword();
- prop.put("password", password);
- Connection conn = null;
- try {
- conn = DriverManager.getConnection(url, prop);
- } finally {
- Arrays.fill(password, (char) 0);
- }
- conn.close();
- }
-}
-</pre>
-<p>
-When using Swing, use <code>javax.swing.JPasswordField</code>.
-</p>
-
-<h3>Passing the User Name and/or Password in the URL</h3>
-<p>
-Instead of passing the user name as a separate parameter as in
-<code>
-Connection conn = DriverManager.
- getConnection("jdbc:h2:~/test", "sa", "123");
-</code>
-the user name (and/or password) can be supplied in the URL itself:
-<code>
-Connection conn = DriverManager.
- getConnection("jdbc:h2:~/test;USER=sa;PASSWORD=123");
-</code>
-The settings in the URL override the settings passed as a separate parameter.
-</p>
-
-<h2 id="password_hash">Password Hash</h2>
-<p>
-Sometimes the database password needs to be stored in a configuration file
-(for example in the <code>web.xml</code> file).
-In addition to connecting with the plain text password,
-this database supports connecting with the password hash.
-This means that only the hash of the password (and not the plain text password)
-needs to be stored in the configuration file.
-This will only protect others from reading or re-constructing the plain text password
-(even if they have access to the configuration file);
-it does not protect others from accessing the database using the password hash.
-</p>
-<p>
-To connect using the password hash instead of plain text password, append
-<code>;PASSWORD_HASH=TRUE</code> to the database URL, and replace
-the password with the password hash. To calculate the password hash from a plain text password,
-run the following command within the H2 Console tool:
-<code>@password_hash <upperCaseUserName> <password></code>.
-As an example, if the user name is <code>sa</code> and the password is
-<code>test</code>, run the command
-<code>@password_hash SA test</code>.
-Then use the resulting password hash as you would use the plain text password.
-When using an encrypted database, then the user password and file password
-need to be hashed separately. To calculate the hash of the file password, run:
-<code>@password_hash file <filePassword></code>.
-</p>
-
-<h2 id="sql_injection">Protection against SQL Injection</h2>
-<h3>What is SQL Injection</h3>
-<p>
-This database engine provides a solution for the security vulnerability known as 'SQL Injection'.
-Here is a short description of what SQL injection means.
-Some applications build SQL statements with embedded user input such as:
-</p>
-<pre>
-String sql = "SELECT * FROM USERS WHERE PASSWORD='"+pwd+"'";
-ResultSet rs = conn.createStatement().executeQuery(sql);
-</pre>
-<p>
-If this mechanism is used anywhere in the application, and user input is not correctly filtered or encoded,
-it is possible for a user to inject SQL functionality or statements by using specially built input
-such as (in this example) this password: <code>' OR ''='</code>.
-In this case the statement becomes:
-</p>
-<pre>
-SELECT * FROM USERS WHERE PASSWORD='' OR ''='';
-</pre>
-<p>
-Which is always true no matter what the password stored in the database is.
-For more information about SQL Injection, see <a href="#glossary_links">Glossary and Links</a>.
-</p>
-
-<h3>Disabling Literals</h3>
-<p>
-SQL Injection is not possible if user input is not directly embedded in SQL statements.
-A simple solution for the problem above is to use a prepared statement:
-</p>
-<pre>
-String sql = "SELECT * FROM USERS WHERE PASSWORD=?";
-PreparedStatement prep = conn.prepareStatement(sql);
-prep.setString(1, pwd);
-ResultSet rs = prep.executeQuery();
-</pre>
-<p>
-This database provides a way to enforce usage of parameters when passing user input
-to the database. This is done by disabling embedded literals in SQL statements.
-To do this, execute the statement:
-</p>
-<pre>
-SET ALLOW_LITERALS NONE;
-</pre>
-<p>
-Afterwards, SQL statements with text and number literals are not allowed any more.
-That means, SQL statement of the form <code>WHERE NAME='abc'</code>
-or <code>WHERE CustomerId=10</code> will fail.
-It is still possible to use prepared statements and parameters as described above. Also, it is still possible to generate
-SQL statements dynamically, and use the Statement API, as long as the SQL statements
-do not include literals.
-There is also a second mode where number literals are allowed:
-<code>SET ALLOW_LITERALS NUMBERS</code>.
-To allow all literals, execute <code>SET ALLOW_LITERALS ALL</code>
-(this is the default setting). Literals can only be enabled or disabled by an administrator.
-</p>
-
-<h3>Using Constants</h3>
-<p>
-Disabling literals also means disabling hard-coded 'constant' literals. This database supports
-defining constants using the <code>CREATE CONSTANT</code> command.
-Constants can be defined only
-when literals are enabled, but used even when literals are disabled. To avoid name clashes
-with column names, constants can be defined in other schemas:
-</p>
-<pre>
-CREATE SCHEMA CONST AUTHORIZATION SA;
-CREATE CONSTANT CONST.ACTIVE VALUE 'Active';
-CREATE CONSTANT CONST.INACTIVE VALUE 'Inactive';
-SELECT * FROM USERS WHERE TYPE=CONST.ACTIVE;
-</pre>
-<p>
-Even when literals are enabled, it is better to use constants instead
-of hard-coded number or text literals in queries or views. With constants, typos are found at compile
-time, the source code is easier to understand and change.
-</p>
-
-<h3>Using the ZERO() Function</h3>
-<p>
-It is not required to create a constant for the number 0 as there is already a built-in function <code>ZERO()</code>:
-</p>
-<pre>
-SELECT * FROM USERS WHERE LENGTH(PASSWORD)=ZERO();
-</pre>
-
-<h2 id="remote_access">Protection against Remote Access</h2>
-<p>
-By default this database does not allow connections from other machines when starting the H2 Console,
-the TCP server, or the PG server. Remote access can be enabled using the command line
-options <code>-webAllowOthers, -tcpAllowOthers, -pgAllowOthers</code>.
-</p>
-<p>
-If you enable remote access using
-<code>-tcpAllowOthers</code> or <code>-pgAllowOthers</code>,
-please also consider using the options <code>-baseDir</code>,
-so that remote users can not create new databases
-or access existing databases with weak passwords.
-When using the option <code>-baseDir</code>, only databases within that directory may be accessed.
-Ensure the existing accessible databases are protected using strong passwords.
-</p>
-<p>
-If you enable remote access using <code>-webAllowOthers</code>,
-please ensure the web server can only be accessed from trusted networks.
-The options <code>-baseDir</code> don't protect
-access to the tools section, prevent remote shutdown of the web server,
-changes to the preferences, the saved connection settings,
-or access to other databases accessible from the system.
-</p>
-
-<h2 id="restricting_classes">Restricting Class Loading and Usage</h2>
-<p>
-By default there is no restriction on loading classes and executing Java code for admins.
-That means an admin may call system functions such as
-<code>System.setProperty</code> by executing:
-</p>
-<pre>
-CREATE ALIAS SET_PROPERTY FOR "java.lang.System.setProperty";
-CALL SET_PROPERTY('abc', '1');
-CREATE ALIAS GET_PROPERTY FOR "java.lang.System.getProperty";
-CALL GET_PROPERTY('abc');
-</pre>
-<p>
-To restrict users (including admins) from loading classes and executing code,
-the list of allowed classes can be set in the system property
-<code>h2.allowedClasses</code>
-in the form of a comma separated list of classes or patterns (items ending with <code>*</code>).
-By default all classes are allowed. Example:
-</p>
-<pre>
-java -Dh2.allowedClasses=java.lang.Math,com.acme.*
-</pre>
-<p>
-This mechanism is used for all user classes, including database event listeners,
-trigger classes, user-defined functions, user-defined aggregate functions, and JDBC
-driver classes (with the exception of the H2 driver) when using the H2 Console.
-</p>
-
-<h2 id="security_protocols">Security Protocols</h2>
-<p>
-The following paragraphs document the security protocols used in this database.
-These descriptions are very technical and only intended for security experts that already know
-the underlying security primitives.
-</p>
-
-<h3>User Password Encryption</h3>
-<p>
-When a user tries to connect to a database, the combination of
-user name, @, and password are hashed using SHA-256, and this hash value
-is transmitted to the database.
-This step does not protect against an attacker that re-uses the value if he is able to listen to the
-(unencrypted) transmission between the client and the server.
-But, the passwords are never transmitted as plain text,
-even when using an unencrypted connection between client and server.
-That means if a user reuses the same password for different things,
-this password is still protected up to some point. See also
-'RFC 2617 - HTTP Authentication: Basic and Digest Access Authentication'
-for more information.
-</p><p>
-When a new database or user is created, a new random salt value is generated.
-The size of the salt is 64 bits. Using the random salt reduces the risk of an
-attacker pre-calculating hash values for many different (commonly used) passwords.
-</p><p>
-The combination of user-password hash value (see above) and salt is hashed
-using SHA-256. The resulting value is stored in the database.
-When a user tries to connect to the database, the database combines
-user-password hash value with the stored salt value and calculates the
-hash value. Other products use multiple iterations (hash the hash value again and again),
-but this is not done in this product to reduce the risk of denial of service attacks
-(where the attacker tries to connect with bogus passwords, and the server
-spends a lot of time calculating the hash value for each password).
-The reasoning is: if the attacker has access to the hashed passwords, he also has
-access to the data in plain text, and therefore does not need the password any more.
-If the data is protected by storing it on another computer and only accessible remotely,
-then the iteration count is not required at all.
-</p>
-
-<h3>File Encryption</h3>
-<p>
-The database files can be encrypted using the AES-128 algorithm.
-</p><p>
-When a user tries to connect to an encrypted database, the combination of
-<code>file@</code> and the file password is hashed using SHA-256. This hash value is
-transmitted to the server.
-</p><p>
-When a new database file is created, a new cryptographically secure
-random salt value is generated. The size of the salt is 64 bits.
-The combination of the file password hash and the salt value is hashed 1024 times
-using SHA-256. The reason for the iteration is to make it harder for an attacker to
-calculate hash values for common passwords.
-</p><p>
-The resulting hash value is used as the key for the block cipher algorithm.
-Then, an initialization vector (IV) key
-is calculated by hashing the key again using SHA-256.
-This is to make sure the IV is unknown to the attacker.
-The reason for using a secret IV is to protect against watermark attacks.
-</p><p>
-Before saving a block of data (each block is 8 bytes long), the following operations are executed:
-first, the IV is calculated by encrypting the block number with the IV key (using the same
-block cipher algorithm). This IV is combined with the plain text using XOR. The resulting data is
-encrypted using the AES-128 algorithm.
-</p><p>
-When decrypting, the operation is done in reverse. First, the block is decrypted using the key,
-and then the IV is calculated combined with the decrypted text using XOR.
-</p><p>
-Therefore, the block cipher mode of operation is CBC (cipher-block chaining), but each chain
-is only one block long. The advantage over the ECB (electronic codebook) mode is that patterns
-in the data are not revealed, and the advantage over multi block CBC is that flipped cipher text bits
-are not propagated to flipped plaintext bits in the next block.
-</p><p>
-Database encryption is meant for securing the database while it is not in use (stolen laptop and so on).
-It is not meant for cases where the attacker has access to files while the database is in use.
-When he has write access, he can for example replace pieces of files with pieces of older versions
-and manipulate data like this.
-</p><p>
-File encryption slows down the performance of the database engine. Compared to unencrypted mode,
-database operations take about 2.5 times longer using AES (embedded mode).
-</p>
-
-<h3>Wrong Password / User Name Delay</h3>
-<p>
-To protect against remote brute force password attacks, the delay after each unsuccessful
-login gets double as long. Use the system properties <code>h2.delayWrongPasswordMin</code>
-and <code>h2.delayWrongPasswordMax</code> to change the minimum (the default is 250 milliseconds)
-or maximum delay (the default is 4000 milliseconds, or 4 seconds). The delay only
-applies for those using the wrong password. Normally there is no delay for a user that knows the correct
-password, with one exception: after using the wrong password, there is a delay of up to (randomly distributed)
-the same delay as for a wrong password. This is to protect against parallel brute force attacks,
-so that an attacker needs to wait for the whole delay. Delays are synchronized. This is also required
-to protect against parallel attacks.
-</p>
-<p>
-There is only one exception message for both wrong user and for wrong password,
-to make it harder to get the list of user names. It is not possible from the stack trace to see
-if the user name was wrong or the password.
-</p>
-
-<h3>HTTPS Connections</h3>
-<p>
-The web server supports HTTP and HTTPS connections using <code>SSLServerSocket</code>.
-There is a default self-certified certificate to support an easy starting point, but
-custom certificates are supported as well.
-</p>
-
-<h2 id="tls_connections">TLS Connections</h2>
-<p>
-Remote TLS connections are supported using the Java Secure Socket Extension
-(<code>SSLServerSocket, SSLSocket</code>). By default, anonymous TLS is enabled.
-</p>
-<p>
-To use your own keystore, set the system properties <code>javax.net.ssl.keyStore</code> and
-<code>javax.net.ssl.keyStorePassword</code> before starting the H2 server and client.
-See also <a href="https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/JSSERefGuide.html#CustomizingStores">
-Customizing the Default Key and Trust Stores, Store Types, and Store Passwords</a>
-for more information.
-</p>
-<p>
-To disable anonymous TLS, set the system property <code>h2.enableAnonymousTLS</code> to false.
-</p>
-
-<h2 id="uuid">Universally Unique Identifiers (UUID)</h2>
-<p>
-This database supports UUIDs. Also supported is a function to create new UUIDs using
-a cryptographically strong pseudo random number generator.
-With random UUIDs, the chance of two having the same value can be calculated
-using the probability theory. See also 'Birthday Paradox'.
-Standardized randomly generated UUIDs have 122 random bits.
-4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz).
-This database supports generating such UUIDs using the built-in function
-<code>RANDOM_UUID()</code> or <code>UUID()</code>.
-Here is a small program to estimate the probability of having two identical UUIDs
-after generating a number of values:
-</p>
-<pre>
-public class Test {
- public static void main(String[] args) throws Exception {
- double x = Math.pow(2, 122);
- for (int i = 35; i < 62; i++) {
- double n = Math.pow(2, i);
- double p = 1 - Math.exp(-(n * n) / 2 / x);
- System.out.println("2^" + i + "=" + (1L << i) +
- " probability: 0" +
- String.valueOf(1 + p).substring(1));
- }
- }
-}
-</pre>
-<p>
-Some values are:
-</p>
-<table class="main">
-<tr><th>Number of UUIs</th><th>Probability of Duplicates</th></tr>
-<tr><td>2^36=68'719'476'736</td><td>0.000'000'000'000'000'4</td></tr>
-<tr><td>2^41=2'199'023'255'552</td><td>0.000'000'000'000'4</td></tr>
-<tr><td>2^46=70'368'744'177'664</td><td>0.000'000'000'4</td></tr>
-</table>
-<p>
-To help non-mathematicians understand what those numbers mean, here a comparison:
-one's annual risk of being hit by a meteorite is estimated to be one chance in 17 billion,
-that means the probability is about 0.000'000'000'06.
-</p>
-
-<h2 id="spatial_features">Spatial Features</h2>
-<p>
-H2 supports the geometry data type and spatial indexes.
-Here is an example SQL script to create a table with a spatial column and index:
-</p>
-<pre>
-CREATE TABLE GEO_TABLE(GID SERIAL, THE_GEOM GEOMETRY);
-INSERT INTO GEO_TABLE(THE_GEOM) VALUES
- ('POINT(500 505)'),
- ('LINESTRING(550 551, 525 512, 565 566)'),
- ('POLYGON ((550 521, 580 540, 570 564, 512 566, 550 521))');
-CREATE SPATIAL INDEX GEO_TABLE_SPATIAL_INDEX
- ON GEO_TABLE(THE_GEOM);
-</pre>
-<p>
-To query the table using geometry envelope intersection,
-use the operation <code>&&</code>, as in PostGIS:
-</p>
-<pre>
-SELECT * FROM GEO_TABLE
- WHERE THE_GEOM &&
- 'POLYGON ((490 490, 536 490, 536 515, 490 515, 490 490))';
-</pre>
-<p>
-You can verify that the spatial index is used using the "explain plan" feature:
-</p>
-<pre>
-EXPLAIN SELECT * FROM GEO_TABLE
- WHERE THE_GEOM &&
- 'POLYGON ((490 490, 536 490, 536 515, 490 515, 490 490))';
--- Result
-SELECT
- "GEO_TABLE"."GID",
- "GEO_TABLE"."THE_GEOM"
-FROM "PUBLIC"."GEO_TABLE"
- /* PUBLIC.GEO_TABLE_SPATIAL_INDEX:
- THE_GEOM &&
- 'POLYGON ((490 490, 536 490, 536 515, 490 515, 490 490))'::Geometry */
-WHERE INTERSECTS("THE_GEOM",
- 'POLYGON ((490 490, 536 490, 536 515, 490 515, 490 490))'::Geometry)
-</pre>
-<p>
-For persistent databases, the spatial index is stored on disk;
-for in-memory databases, the index is kept in memory.
-</p>
-
-<h2 id="recursive_queries">Recursive Queries</h2>
-<p>
-H2 has experimental support for recursive queries using so called "common table expressions" (CTE).
-Examples:
-</p>
-<pre>
-WITH RECURSIVE T(N) AS (
- SELECT 1
- UNION ALL
- SELECT N+1 FROM T WHERE N<10
-)
-SELECT * FROM T;
--- returns the values 1 .. 10
-
-WITH RECURSIVE T(N) AS (
- SELECT 1
- UNION ALL
- SELECT N*2 FROM T WHERE N<10
-)
-SELECT * FROM T;
--- returns the values 1, 2, 4, 8, 16
-
-CREATE TABLE FOLDER(ID INT PRIMARY KEY, NAME VARCHAR(255), PARENT INT);
-
-INSERT INTO FOLDER VALUES(1, null, null), (2, 'src', 1),
-(3, 'main', 2), (4, 'org', 3), (5, 'test', 2);
-
-WITH LINK(ID, NAME, LEVEL) AS (
- SELECT ID, NAME, 0 FROM FOLDER WHERE PARENT IS NULL
- UNION ALL
- SELECT FOLDER.ID, IFNULL(LINK.NAME || '/', '') || FOLDER.NAME, LEVEL + 1
- FROM LINK INNER JOIN FOLDER ON LINK.ID = FOLDER.PARENT
-)
-SELECT NAME FROM LINK WHERE NAME IS NOT NULL ORDER BY ID;
--- src
--- src/main
--- src/main/org
--- src/test
-</pre>
-<p>
-Limitations: Recursive queries need to be of the type <code>UNION ALL</code>,
-and the recursion needs to be on the second part of the query.
-No tables or views with the name of the table expression may exist.
-Different table expression names need to be used when using multiple distinct table
-expressions within the same transaction and for the same session.
-All columns of the table expression are of type <code>VARCHAR</code>,
-and may need to be cast to the required data type.
-Views with recursive queries are not supported.
-Subqueries and <code>INSERT INTO ... FROM</code> with recursive queries are not supported.
-Parameters are only supported within the last <code>SELECT</code> statement
-(a workaround is to use session variables like <code>@start</code>
-within the table expression).
-The syntax is:
-</p>
-<pre>
-WITH RECURSIVE recursiveQueryName(columnName, ...) AS (
- nonRecursiveSelect
- UNION ALL
- recursiveSelect
-)
-select
-</pre>
-
-<h2 id="system_properties">Settings Read from System Properties</h2>
-<p>
-Some settings of the database can be set on the command line using
-<code>-DpropertyName=value</code>. It is usually not required to change those settings manually.
-The settings are case sensitive.
-Example:
-</p>
-<pre>
-java -Dh2.serverCachedObjects=256 org.h2.tools.Server
-</pre>
-<p>
-The current value of the settings can be read in the table
-<code>INFORMATION_SCHEMA.SETTINGS</code>.
-</p>
-<p>
-For a complete list of settings, see
-<a href="http://www.h2database.com/javadoc/org/h2/engine/SysProperties.html">SysProperties</a>.
-</p>
-
-<h2 id="server_bind_address">Setting the Server Bind Address</h2>
-<p>
-Usually server sockets accept connections on any/all local addresses.
-This may be a problem on multi-homed hosts.
-To bind only to one address, use the system property <code>h2.bindAddress</code>.
-This setting is used for both regular server sockets and for TLS server sockets.
-IPv4 and IPv6 address formats are supported.
-</p>
-
-<h2 id="file_system">Pluggable File System</h2>
-<p>
-This database supports a pluggable file system API.
-The file system implementation is selected using a file name prefix.
-Internally, the interfaces are very similar to the Java 7 NIO2 API, but do not (yet) use or require Java 7.
-The following file systems are included:
-</p>
-<ul><li><code>zip:</code> read-only zip-file based file system. Format: <code>zip:/zipFileName!/fileName</code>.
-</li><li><code>split:</code> file system that splits files in 1 GB files (stackable with other file systems).
-</li><li><code>nio:</code> file system that uses <code>FileChannel</code> instead of <code>RandomAccessFile</code> (faster in some operating systems).
-</li><li><code>nioMapped:</code> file system that uses memory mapped files (faster in some operating systems).
- Please note that there currently is a file size limitation of 2 GB when using this file system.
- To work around this limitation, combine it with the split file system: <code>split:nioMapped:test</code>.
-</li><li><code>async:</code> experimental file system that uses <code>AsynchronousFileChannel</code> instead of <code>RandomAccessFile</code> (faster in some operating systems).
-</li><li><code>memFS:</code> in-memory file system (slower than mem; experimental; mainly used for testing the database engine itself).
-</li><li><code>memLZF:</code> compressing in-memory file system (slower than memFS but uses less memory; experimental; mainly used for testing the database engine itself).
-</li><li><code>nioMemFS:</code> stores data outside of the VM's heap - useful for large memory DBs without incurring GC costs.
-</li>
-<li>
- <code>nioMemLZF:</code> stores compressed data outside of the VM's heap -
- useful for large memory DBs without incurring GC costs.
- Use "nioMemLZF:12:" to tweak the % of blocks that are stored uncompressed.
- If you size this to your working set correctly,
- compressed storage is roughly the same performance as uncompressed.
- The default value is 1%.
-</li></ul>
-<p>
-As an example, to use the <code>nio</code> file system with PageStore storage engine,
-use the following database URL: <code>jdbc:h2:nio:~/test;MV_STORE=FALSE</code>.
-With MVStore storage engine nio file system is used by default.
-</p>
-<p>
-To register a new file system, extend the classes <code>org.h2.store.fs.FilePath, FileBase</code>,
-and call the method <code>FilePath.register</code> before using it.
-</p>
-<p>
-For input streams (but not for random access files), URLs may be used in addition to the registered file systems.
-Example: <code>jar:file:///c:/temp/example.zip!/org/example/nested.csv</code>.
-To read a stream from the classpath, use the prefix <code>classpath:</code>, as in
-<code>classpath:/org/h2/samples/newsfeed.sql</code>.
-</p>
-
-<h2 id="file_system_split">Split File System</h2>
-<p>
-The file system prefix <code>split:</code> is used to split logical files into multiple physical files,
-for example so that a database can get larger than the maximum file system size of the operating system.
-If the logical file is larger than the maximum file size, then the file is split as follows:
-</p>
-<ul><li><code><fileName></code> (first block, is always created)
-</li><li><code><fileName>.1.part</code> (second block)
-</li></ul>
-<p>
-More physical files (<code>*.2.part, *.3.part</code>) are automatically created / deleted if needed.
-The maximum physical file size of a block is 2^30 bytes, which is also called 1 GiB or 1 GB.
-However this can be changed if required, by specifying the block size in the file name.
-The file name format is: <code>split:<x>:<fileName></code> where the file size per block is 2^x.
-For 1 MiB block sizes, use x = 20 (because 2^20 is 1 MiB).
-The following file name means the logical file is split into 1 MiB blocks: <code>split:20:test.h2.db</code>.
-An example database URL for this case is <code>jdbc:h2:split:20:~/test</code>.
-</p>
-
-<h2 id="database_upgrade">Database Upgrade</h2>
-<p>
-In version 1.2, H2 introduced a new file store implementation which is incompatible to the one used in versions < 1.2.
-To automatically convert databases to the new file store, it is necessary to include an additional jar file.
-The file can be found at <a href="http://h2database.com/h2mig_pagestore_addon.jar">http://h2database.com/h2mig_pagestore_addon.jar</a> .
-If this file is in the classpath, every connect to an older database will result in a conversion process.
-</p>
-<p>
-The conversion itself is done internally via <code>'script to'</code> and <code>'runscript from'</code>. After the conversion process, the files will be
-renamed from
-</p>
-<ul>
-<li><code>dbName.data.db</code> to <code>dbName.data.db.backup</code>
-</li><li><code>dbName.index.db</code> to <code>dbName.index.db.backup</code>
-</li></ul>
-<p>
-by default. Also, the temporary script will be written to the database directory instead of a temporary directory.
-Both defaults can be customized via
-</p>
-<ul>
-<li><code>org.h2.upgrade.DbUpgrade.setDeleteOldDb(boolean)</code>
-</li><li><code>org.h2.upgrade.DbUpgrade.setScriptInTmpDir(boolean)</code>
-</li></ul>
-<p>
-prior opening a database connection.
-</p>
-<p>
-Since version 1.2.140 it is possible to let the old h2 classes (v 1.2.128) connect to the database.
-The automatic upgrade .jar file must be present, and the URL must start with <code>jdbc:h2v1_1:</code>
-(the JDBC driver class is <code>org.h2.upgrade.v1_1.Driver</code>).
-If the database should automatically connect using the old version if a database with the old format exists
-(without upgrade), and use the new version otherwise, then append <code>;NO_UPGRADE=TRUE</code>
-to the database URL.
-Please note the old driver did not process the system property <code>"h2.baseDir"</code> correctly,
-so that using this setting is not supported when upgrading.
-</p>
-
-<h2 id="java_objects_serialization">Java Objects Serialization</h2>
-<p>
-Java objects serialization is enabled by default for columns of type <code>OTHER</code>, using standard Java serialization/deserialization semantics.
-</p>
-<p>
-To disable this feature set the system property <code>h2.serializeJavaObject=false</code> (default: true).
-</p>
-<p>
-Serialization and deserialization of java objects is customizable both at system level and at database level providing a
-<a href="http://www.h2database.com/javadoc/org/h2/api/JavaObjectSerializer.html">JavaObjectSerializer</a> implementation:
-</p>
-<ul>
-<li>
-At system level set the system property <code>h2.javaObjectSerializer</code> with the
-Fully Qualified Name of the <code>JavaObjectSerializer</code> interface implementation.
-It will be used over the entire JVM session to (de)serialize java objects being stored in column of type OTHER.
-Example <code>h2.javaObjectSerializer=com.acme.SerializerClassName</code>.
-</li>
-<li>
-At database level execute the SQL statement <code>SET JAVA_OBJECT_SERIALIZER 'com.acme.SerializerClassName'</code>
-or append <code>;JAVA_OBJECT_SERIALIZER='com.acme.SerializerClassName'</code> to the database URL: <code>jdbc:h2:~/test;JAVA_OBJECT_SERIALIZER='com.acme.SerializerClassName'</code>.
-<p>
-Please note that this SQL statement can only be executed before any tables are defined.
-</p>
-</li>
-</ul>
-
-<h2 id="custom_data_types_handler_api">Custom Data Types Handler API</h2>
-<p>
-It is possible to extend the type system of the database by providing your own implementation
-of minimal required API basically consisting of type identification and conversion routines.
-</p>
-<p>
-In order to enable this feature, set the system property <code>h2.customDataTypesHandler</code> (default: null) to the fully qualified name of the class providing
-<a href="http://www.h2database.com/javadoc/org/h2/api/CustomDataTypesHandler.html">CustomDataTypesHandler</a> interface implementation. <br />
-The instance of that class will be created by H2 and used to:
-</p>
-<ul>
-<li>resolve the names and identifiers of extrinsic data types.
-</li>
-<li>convert values of extrinsic data types to and from values of built-in types.
-</li>
-<li>provide order of the data types.
-</li>
-</ul>
-<p>This is a system-level setting, i.e. affects all the databases.</p>
-
-<p><b>Note: </b>Please keep in mind that this feature may not possibly provide the same ABI stability level as other features as it exposes many of the H2 internals. You may be required to update your code occasionally due to internal changes in H2 if you are going to use this feature.
-</p>
-
-
-<h2 id="limits_limitations">Limits and Limitations</h2>
-<p>
-This database has the following known limitations:
-</p>
-<ul>
-<li>Database file size limit:
- 4 TB (using the default page size of 2 KB) or higher (when using a larger page size).
- This limit is including CLOB and BLOB data.
-</li><li>The maximum file size for FAT or FAT32 file systems is 4 GB.
- That means when using FAT or FAT32, the limit is 4 GB for the data. This is the limitation of the file system.
- The database does provide a workaround for this problem, it is to use the file name prefix <code>split:</code>.
- In that case files are split into files of 1 GB by default.
- An example database URL is: <code>jdbc:h2:split:~/test</code>.
-</li><li>The maximum number of rows per table is 2^64.
-</li><li>The maximum number of open transactions is 65535.
-</li><li>Main memory requirements: The larger the database, the more main memory is required.
- With the current storage mechanism (the page store),
- the minimum main memory required is around 1 MB for each 8 GB database file size.
-</li><li>Limit on the complexity of SQL statements.
-Statements of the following form will result in a stack overflow exception:
-<pre>
-SELECT * FROM DUAL WHERE X = 1
-OR X = 2 OR X = 2 OR X = 2 OR X = 2 OR X = 2
--- repeat previous line 500 times --
-</pre>
-</li><li>There is no limit for the following entities, except the memory and storage capacity:
- maximum identifier length (table name, column name, and so on);
- maximum number of tables, columns, indexes, triggers, and other database objects;
- maximum statement length, number of parameters per statement, tables per statement, expressions
- in order by, group by, having, and so on;
- maximum rows per query;
- maximum columns per table, columns per index, indexes per table, lob columns per table, and so on;
- maximum row length, index row length, select row length;
- maximum length of a varchar column, decimal column, literal in a statement.
-</li><li>Querying from the metadata tables is slow if there are many tables (thousands).
-</li><li>For limitations on data types, see the documentation of the respective Java data type
- or the data type documentation of this database.
-</li></ul>
-
-<h2 id="glossary_links">Glossary and Links</h2>
-<table class="main">
- <tr>
- <th>Term</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>AES-128</td>
- <td>A block encryption algorithm. See also: <a
- href="https://en.wikipedia.org/wiki/Advanced_Encryption_Standard">Wikipedia:
- Advanced Encryption Standard</a></td>
- </tr>
- <tr>
- <td>Birthday Paradox</td>
- <td>Describes the higher than expected probability that two
- persons in a room have the same birthday. Also valid for randomly
- generated UUIDs. See also: <a
- href="https://en.wikipedia.org/wiki/Birthday_problem">Wikipedia:
- Birthday problem</a></td>
- </tr>
- <tr>
- <td>Digest</td>
- <td>Protocol to protect a password (but not to protect data).
- See also: <a href="https://www.ietf.org/rfc/rfc2617.txt">RFC
- 2617: HTTP Digest Access Authentication</a></td>
- </tr>
- <tr>
- <td>HTTPS</td>
- <td>A protocol to provide security to HTTP connections. See
- also: <a href="https://www.ietf.org/rfc/rfc2818.txt">RFC 2818:
- HTTP Over TLS</a></td>
- </tr>
- <tr>
- <td>Modes of Operation</td>
- <td><a
- href="https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation">Wikipedia:
- Block cipher mode of operation</a></td>
- </tr>
- <tr>
- <td>Salt</td>
- <td>Random number to increase the security of passwords. See
- also: <a href="https://en.wikipedia.org/wiki/Key_derivation_function">Wikipedia:
- Key derivation function</a></td>
- </tr>
- <tr>
- <td>SHA-256</td>
- <td>A cryptographic one-way hash function. See also: <a
- href="https://en.wikipedia.org/wiki/Secure_Hash_Algorithms">Wikipedia:
- Secure Hash Algorithms</a></td>
- </tr>
- <tr>
- <td>SQL Injection</td>
- <td>A security vulnerability where an application embeds SQL
- statements or expressions in user input. See also: <a
- href="https://en.wikipedia.org/wiki/SQL_injection">Wikipedia:
- SQL injection</a></td>
- </tr>
- <tr>
- <td>Watermark Attack</td>
- <td>Security problem of certain encryption programs where the
- existence of certain data can be proven without decrypting. For more
- information, search in the internet for 'watermark attack
- cryptoloop'</td>
- </tr>
- <tr>
- <td>SSL/TLS</td>
- <td>Secure Sockets Layer / Transport Layer Security. See also:
- <a href="https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/JSSERefGuide.html">Java Secure Socket
- Extension (JSSE)</a></td>
- </tr>
-</table>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/architecture.html b/modules/h2/src/docsrc/html/architecture.html
deleted file mode 100644
index f9b2946..0000000
--- a/modules/h2/src/docsrc/html/architecture.html
+++ /dev/null
@@ -1,154 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Architecture
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Architecture</h1>
-<a href="#introduction">
- Introduction</a><br />
-<a href="#top_down">
- Top-down overview</a><br />
-<a href="#jdbc">
- JDBC driver</a><br />
-<a href="#connection">
- Connection/session management</a><br />
-<a href="#command">
- Command execution and planning</a><br />
-<a href="#table">
- Table/index/constraints</a><br />
-<a href="#transaction">
- Undo log, redo log, and transactions layer</a><br />
-<a href="#btree">
- B-tree engine and page-based storage allocation</a><br />
-<a href="#filesystem">
- Filesystem abstraction</a><br />
-
-<h2 id="introduction">Introduction</h2>
-<p>
-H2 implements an embedded and standalone ANSI-SQL89 compliant SQL engine on top of a B-tree based disk store.
-</p>
-<p>
-As of October 2013, Thomas is still working on our next-generation storage engine called MVStore. This will
-in time replace the B-tree based storage engine.
-</p>
-
-<h2 id="top_down">Top-down Overview</h2>
-<p>
-Working from the top down, the layers look like this:
-<ul><li>JDBC driver.
-</li><li>Connection/session management.
-</li><li>SQL Parser.
-</li><li>Command execution and planning.
-</li><li>Table/Index/Constraints.
-</li><li>Undo log, redo log, and transactions layer.
-</li><li>B-tree engine and page-based storage allocation.
-</li><li>Filesystem abstraction.
-</li></ul>
-</p>
-
-<h2 id="jdbc">JDBC Driver</h2>
-<p>
-The JDBC driver implementation lives in <code>org.h2.jdbc, org.h2.jdbcx</code>
-</p>
-
-<h2 id="connection">Connection/session management</h2>
-<p>
-The primary classes of interest are:
-<table class="main">
-<tr><th>Package</th><th>Description</th></tr>
-<tr><td>org.h2.engine.Database</td><td>the root/global class</td></tr>
-<tr><td>org.h2.engine.SessionInterface</td>
- <td>abstracts over the differences between embedded and remote sessions</td></tr>
-<tr><td>org.h2.engine.Session</td>
- <td>local/embedded session</td></tr>
-<tr><td>org.h2.engine.SessionRemote</td>
- <td>remote session</td></tr>
-</table>
-</p>
-
-<h2 id="jdbc">Parser</h2>
-<p>
-The parser lives in <code>org.h2.command.Parser</code>. It uses a straightforward recursive-descent design.
-</p>
-<p>
-See Wikipedia <a href="https://en.wikipedia.org/wiki/Recursive_descent_parser">Recursive descent parser</a> page.
-</p>
-
-
-<h2 id="command">Command execution and planning</h2>
-<p>
-Unlike other databases, we do not have an intermediate step where we generate some kind of IR (intermediate representation) of the query.
-The parser class directly generates a command execution object.
-Then we run some optimisation steps over the command to possibly generate a more efficient command.
-
-The primary packages of interest are:
-<table class="main">
-<tr><th>Package</th><th>Description</th></tr>
-<tr><td>org.h2.command.ddl</td><td>Commands that modify schema data structures</td></tr>
-<tr><td>org.h2.command.dml</td><td>Commands that modify data</td></tr>
-</table>
-</p>
-
-<h2 id="table">Table/Index/Constraints</h2>
-<p>
-One thing to note here is that indexes are simply stored as special kinds of tables.
-</p>
-<p>
-The primary packages of interest are:
-<table class="main">
-<tr><th>Package</th><th>Description</th></tr>
-<tr><td>org.h2.table</td><td>Implementations of different kinds of tables</td></tr>
-<tr><td>org.h2.index</td><td>Implementations of different kinds of indices</td></tr>
-</table>
-</p>
-
-<h2 id="transaction">Undo log, redo log, and transactions layer</h2>
-<p>
-We have a transaction log, which is shared among all sessions. See also
-<a href="https://en.wikipedia.org/wiki/Transaction_log">https://en.wikipedia.org/wiki/Transaction_log</a>
-<a href="http://h2database.com/html/grammar.html#set_log">http://h2database.com/html/grammar.html#set_log</a>
-</p>
-<p>
-We also have an undo log, which is per session, to undo an operation (an update that fails for example)
-and to rollback a transaction.
-Theoretically, the transaction log could be used, but for simplicity, H2 currently uses it's
-own "list of operations" (usually in-memory).
-</p>
-<p>
-With the MVStore, this is no longer needed (just the transaction log).
-</p>
-
-<h2 id="btree">B-tree engine and page-based storage allocation.</h2>
-<p>
-The primary package of interest is <code>org.h2.store</code>.
-</p>
-<p>
-This implements a storage mechanism which allocates pages of storage (typically 2k in size)
-and also implements a b-tree over those pages to allow fast retrieval and update.
-</p>
-
-<h2 id="filesystem">Filesystem abstraction.</h2>
-<p>
-The primary class of interest is <code>org.h2.store.FileStore</code>.
-</p>
-<p>
-This implements an abstraction of a random-access file.
-This allows the higher layers to treat in-memory vs. on-disk vs. zip-file databases the same.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/build.html b/modules/h2/src/docsrc/html/build.html
deleted file mode 100644
index c516e77..0000000
--- a/modules/h2/src/docsrc/html/build.html
+++ /dev/null
@@ -1,325 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Build
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1 id="build_index">Build</h1>
-<a href="#portability">
- Portability</a><br />
-<a href="#environment">
- Environment</a><br />
-<a href="#building">
- Building the Software</a><br />
-<a href="#build_targets">
- Build Targets</a><br />
-<a href="#maven2">
- Using Maven 2</a><br />
-<a href="#using_eclipse">
- Using Eclipse</a><br />
-<a href="#translating">
- Translating</a><br />
-<a href="#providing_patches">
- Submitting Source Code Changes</a><br />
-<a href="#support">
- Reporting Problems or Requests</a><br />
-<a href="#automated">
- Automated Build</a><br />
-<a href="#railroad">
- Generating Railroad Diagrams</a><br />
-
-<h2 id="portability">Portability</h2>
-<p>
-This database is written in Java and therefore works on many platforms.
-</p>
-
-<h2 id="environment">Environment</h2>
-<p>
-To run this database, a Java Runtime Environment (JRE) version 7 or higher is required.
-</p>
-<p>
-To create the database executables, the following software stack was used.
-To use this database, it is not required to install this software however.
-</p>
-<ul><li>Mac OS X and Windows
-</li><li><a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Oracle JDK Version 7</a>
-(version 7 is not available for free download any more)
-</li><li><a href="http://www.eclipse.org">Eclipse</a>
-</li><li>Eclipse Plugins:
- <a href="http://subclipse.tigris.org">Subclipse</a>,
- <a href="https://checkstyle.github.io/eclipse-cs/">Eclipse Checkstyle Plug-in</a>,
- <a href="http://www.eclemma.org">EclEmma Java Code Coverage</a>
-</li><li><a href="https://www.mozilla.com/firefox">Mozilla Firefox</a>
-</li><li><a href="http://www.openoffice.org">OpenOffice</a>
-</li><li><a href="http://nsis.sourceforge.net">NSIS</a> (Nullsoft Scriptable Install System)
-</li><li><a href="http://maven.apache.org">Maven</a>
-</li></ul>
-
-<h2 id="building">Building the Software</h2>
-<p>
-You need to install a JDK, for example the Oracle JDK version 7 or 8.
-Ensure that Java binary directory is included in the <code>PATH</code> environment variable, and that
-the environment variable <code>JAVA_HOME</code> points to your Java installation.
-On the command line, go to the directory <code>h2</code> and execute the following command:
-</p>
-<pre>
-build -?
-</pre>
-<p>
-For Linux and OS X, use <code>./build.sh</code> instead of <code>build</code>.
-</p>
-<p>
-You will get a list of targets. If you want to build the <code>jar</code> file, execute (Windows):
-</p>
-<pre>
-build jar
-</pre>
-<p>
-To run the build tool in shell mode, use the command line option <code>-</code>:
-</p>
-<pre>
-./build.sh -
-</pre>
-
-<h2 id="build_targets">Build Targets</h2>
-<p>
-The build system can generate smaller jar files as well. The following targets are currently supported:
-</p>
-<ul><li><code>jarClient</code>
- creates the file <code>h2client.jar</code>. This only contains the JDBC client.
-</li><li><code>jarSmall</code>
- creates the file <code>h2small.jar</code>.
- This only contains the embedded database. Debug information is disabled.
-</li><li><code>javadocImpl</code> creates the Javadocs of the implementation.
-</li></ul>
-<p>
-To create the file <code>h2client.jar</code>, go to the directory <code>h2</code> and execute the following command:
-</p>
-<pre>
-build jarClient
-</pre>
-
-<h3>Using Apache Lucene</h3>
-<p>
-Apache Lucene 5.5.5 is used for testing.
-Newer versions up to 7.7.1 can also be used.
-</p>
-
-<h2 id="maven2">Using Maven 2</h2>
-<h3>Using a Central Repository</h3>
-<p>
-You can include the database in your Maven 2 project as a dependency.
-Example:
-</p>
-<pre>
-<dependency>
- <groupId>com.h2database</groupId>
- <artifactId>h2</artifactId>
- <version>${version}</version>
-</dependency>
-</pre>
-<p>
-New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically
-synchronized with the main <a href="http://repo2.maven.org/maven2/com/h2database/h2/">Maven repository</a>;
-however after a new release it may take a few hours before they are available there.
-</p>
-<h3>Maven Plugin to Start and Stop the TCP Server</h3>
-<p>
-A Maven plugin to start and stop the H2 TCP server is available from
-<a href="https://github.com/ljnelson/h2-maven-plugin">Laird Nelson at GitHub</a>.
-To start the H2 server, use:
-</p>
-<pre>
-mvn com.edugility.h2-maven-plugin:1.0-SNAPSHOT:spawn
-</pre>
-<p>
-To stop the H2 server, use:
-</p>
-<pre>
-mvn com.edugility.h2-maven-plugin:1.0-SNAPSHOT:stop
-</pre>
-
-<h3>Using Snapshot Version</h3>
-<p>
-To build a <code>h2-*-SNAPSHOT.jar</code> file and upload it the to the local Maven 2 repository, execute the following command:
-</p>
-<pre>
-build mavenInstallLocal
-</pre>
-<p>
-Afterwards, you can include the database in your Maven 2 project as a dependency:
-</p>
-<pre>
-<dependency>
- <groupId>com.h2database</groupId>
- <artifactId>h2</artifactId>
- <version>1.0-SNAPSHOT</version>
-</dependency>
-</pre>
-
-<h2 id="using_eclipse">Using Eclipse</h2>
-<p>
-To create an Eclipse project for H2, use the following steps:
-</p>
-<ul><li>Install Git and <a href="http://www.eclipse.org">Eclipse</a>.
-</li><li>Get the H2 source code from Github:<br />
- <code>git clone https://github.com/h2database/h2database</code>
-</li><li>Download all dependencies:<br />
- <code>build.bat download</code>(Windows)<br />
- <code>./build.sh download</code>(otherwise)<br />
-</li><li>In Eclipse, create a new Java project from existing source code:
- <code>File, New, Project, Java Project, Create project from existing source</code>.
-</li><li>Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
-</li><li>To resolve <code>com.sun.javadoc</code> import statements,
- you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
-</li></ul>
-
-<h2 id="translating">Translating</h2>
-<p>
-The translation of this software is split into the following parts:
-</p>
-<ul>
-<li>H2 Console: <code>src/main/org/h2/server/web/res/_text_*.prop</code>
-</li><li>Error messages: <code>src/main/org/h2/res/_messages_*.prop</code>
-</li></ul>
-<p>
-To translate the H2 Console, start it and select Preferences / Translate.
-After you are done, send the translated <code>*.prop</code> file to the Google Group.
-The web site is currently translated using Google.
-</p>
-
-<h2 id="providing_patches">Submitting Source Code Changes</h2>
-<p>
-If you'd like to contribute bug fixes or new features, please consider the following guidelines to simplify merging them:
-</p>
-<ul><li>Only use Java 7 features (do not use Java 8/9/etc) (see <a href="#environment">Environment</a>).
-</li><li>Follow the coding style used in the project, and use Checkstyle (see above) to verify.
- For example, do not use tabs (use spaces instead).
- The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>.
-</li><li>A template of the Eclipse settings are in
- <code>src/installer/eclipse.settings/*</code>. If you want to use them,
- you need to copy them to the <code>.settings</code> directory.
- The formatting options (<code>eclipseCodeStyle</code>) are also included.
-</li><li>Please provide test cases and integrate them into the test suite.
- For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>.
- For SQL level tests, see SQL files in <code>src/test/org/h2/test/scripts</code>.
-</li><li>The test cases should cover at least 90% of the changed and new code;
- use a code coverage tool to verify that (see above).
- or use the build target <code>coverage</code>.
-</li><li>Verify that you did not break other features: run the test cases by executing
- <code>build test</code>.
-</li><li>Provide end user documentation if required (<code>src/docsrc/html/*</code>).
-</li><li>Document grammar changes in <code>src/docsrc/help/help.csv</code>
-</li><li>Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
-</li><li>Verify the spelling using <code>build spellcheck</code>. If required
- add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code>.
-</li><li>Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
-</li><li>Verify the formatting using <code>build docs</code> and
- <code>build javadoc</code>.
-</li><li>Submit changes using GitHub's "pull requests". You'll require a free <a href="https://github.com/">GitHub</a>
- account. If you are not familiar with pull requests, please read GitHub's
- <a href="https://help.github.com/articles/using-pull-requests/">Using pull requests</a> page.
-</li></ul>
-<p>
-For legal reasons, patches need to be public in the form of an
- <a href="https://github.com/h2database/h2database/issues">issue report or attachment</a> or in the form of an email
- to the <a href="https://groups.google.com/group/h2-database">group</a>.
-Significant contributions need to include the following statement:
-</p>
-<p>
-"I wrote the code, it's mine, and I'm contributing it to H2 for distribution
-multiple-licensed under the MPL 2.0, and the EPL 1.0
-(http://h2database.com/html/license.html)."
-</p>
-
-<h2 id="support">Reporting Problems or Requests</h2>
-<p>
-Please consider the following checklist if you have a question, want to report a problem,
-or if you have a feature request:
-</p>
-<ul><li>For bug reports, please provide a
- <a href="http://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
-</li><li>Feature requests are always welcome, even if the feature is already on the
- <a href="http://www.h2database.com/html/roadmap.html">roadmap</a>. Your mail will help prioritize feature requests.
- If you urgently need a feature, consider <a href="#providing_patches">providing a patch</a>.
-</li><li>Before posting problems, check the
- <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
-</li><li>When got an unexpected exception, please try the
- <a href="http://www.h2database.com/html/sourceError.html">Error Analyzer tool</a>. If this doesn't help,
- please report the problem, including the complete error message and stack trace,
- and the root cause stack trace(s).
-</li><li>When sending source code, please use a public web clipboard such as
- <a href="https://pastebin.com/">Pastebin</a> or
- <a href="http://www.mysticpaste.com/new">Mystic Paste</a>
- to avoid formatting problems.
- Please keep test cases as simple and short as possible,
- but so that the problem can still be reproduced.
- As a template, use:
- <a href="https://github.com/h2database/h2database/tree/master/h2/src/test/org/h2/samples/HelloWorld.java">HelloWorld.java</a>.
- Method that simply call other methods should be avoided,
- as well as unnecessary exception handling.
- Please use the JDBC API and no external tools or libraries.
- The test should include all required initialization code, and
- should be started with the main method.
-</li><li>For large attachments, use a public storage such as
- <a href="https://www.google.com/drive/">Google Drive</a>.
-</li><li>Google Group versus issue tracking:
- Use the
- <a href="http://groups.google.com/group/h2-database">Google Group</a>
- for questions or if you are not sure it's a bug.
- If you are sure it's a bug, you can create an
- <a href="https://github.com/h2database/h2database/issues">issue</a>,
- but you don't need to (sending an email to the group is enough).
- Please note that only few people monitor the issue tracking system.
-</li><li>For out-of-memory problems, please analyze the problem yourself first,
- for example using the command line option
- <code>-XX:+HeapDumpOnOutOfMemoryError</code>
- (to create a heap dump file on out of memory)
- and a memory analysis tool such as the
- <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
-</li><li>It may take a few days to get an answers. Please do not double post.
-</li></ul>
-
-<h2 id="automated">Automated Build</h2>
-<p>
-This build process is automated and runs regularly.
-The build process includes running the tests and code coverage, using the command line
-<code>./build.sh clean jar coverage -Dh2.ftpPassword=... uploadBuild</code>.
-The last results are available here:
-</p>
-<ul><li><a href="http://h2database.com/html/testOutput.html">Test Output</a>
-</li><li><a href="http://h2database.com/coverage/overview.html">Code Coverage Summary</a>
-</li><li><a href="http://h2database.com/coverage/coverage.zip">Code Coverage Details (download, 1.3 MB)</a>
-</li><li><a href="http://www.h2database.com/automated/news.xml">Build Newsfeed</a>
-</li></ul>
-
-<h2 id="railroad">Generating Railroad Diagrams</h2>
-<p>
-The railroad diagrams of the <a href="grammar.html">SQL grammar</a> are HTML, formatted as nested tables.
-The diagrams are generated as follows:
-</p>
-<ul><li>The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
-</li><li>The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
-</li><li>The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
-</li></ul>
-<p>
-To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>.
-This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/changelog.html b/modules/h2/src/docsrc/html/changelog.html
deleted file mode 100644
index 6a36a27..0000000
--- a/modules/h2/src/docsrc/html/changelog.html
+++ /dev/null
@@ -1,1487 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Change Log
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Change Log</h1>
-
-<h2>Next Version (unreleased)</h2>
-<ul>
-<li>-
-</li>
-</ul>
-
-<h2>Version 1.4.199 (2019-03-13)</h2>
-<ul>
-<li>PR #1807: Reduce code duplication and remove h2.mixedGeometries
-</li>
-<li>PR #1806: Improve SELECT FOR UPDATE documentation
-</li>
-<li>PR #1804: Lift limit of 10 characters on enum value (1.4.198 regression)
-</li>
-<li>PR #1803: Do not rely on index sorting in SELECT FOR UPDATE
-</li>
-<li>Issue #1800: Remove experimental status from window functions
-</li>
-<li>PR #1799: Fire triggers after row locking and remove some leftovers
-</li>
-<li>PR #1798: Reuse some string builders, remove StatementBuilder and other minor changes
-</li>
-<li>Issue #1795: 1.4.198 regression with batch updates and transactions
-</li>
-<li>PR #1794: Ask password in Shell in secure way and improve database creation information in tutorial
-</li>
-<li>PR #1791: Move commands to commands.html and other changes
-</li>
-<li>Issue #1774: H2 Browser configuration is unclear and fails on KUbuntu
-</li>
-<li>PR #1790: Do not convert standard TRIM function to non-standard functions
-</li>
-<li>Issue #1787: Non-standard MERGE throws LOCK_TIMEOUT_1 on violation of some constraints
-</li>
-<li>PR #1784: improve database not found error
-</li>
-<li>Issue #1740: Enhancement Request: h2 server: do not swallow exceptions
-</li>
-<li>Issue #1616: Metadata and scripts should be persisted with unconditionally quoted identifiers
-</li>
-<li>PR #1779: Improve isSimpleIdentifier() and enquoteIdentifier()
-</li>
-<li> PR #1776: Improve DATABASE_TO_LOWER handling
-</li>
-<li>Issue #1771: NPE in Comparison.createIndexConditions
-</li>
-<li>PR #1772: Fix newlines in test scripts
-</li>
-<li>Issue #1762: NullPointerException in Parser. Introduced in 1.4.198
-</li>
-<li>PR #1768: Add more context-sensitive keywords
-</li>
-<li>Issue #1758: sequence restart issue with 1.4.198
-</li>
-<li>Issue #1759: SELECT … FOR UPDATE returns old data in 1.4.198
-</li>
-<li>PR #1756: Fix DISTINCT ON in presence of ORDER BY
-</li>
-<li>PR #1754: Fix window functions in JOIN with ON condition
-</li>
-<li>Issue #1751: making it easier to open console and create local databases
-</li>
-<li>Issue #1750: JOIN t ON t.col IN (SELECT ...) throws AssertionError
-</li>
-</ul>
-
-<h2>Version 1.4.198 (2019-02-22)</h2>
-<ul>
-<li>Issue #1746: Infinite loop in TestConcurrent.testConcurrentChangeAndGetVersion()
-</li>
-<li>Issue #1739: Table and view names not case sensitive when using DATABASE_TO_UPPER=FALSE
-</li>
-<li>Issue #848: H2 PostgreSQL Compatibility Mode: lowercase metadata
-</li>
-<li>Issue #485: Problem is in invalid case for schema's IGNORECASE=true;DATABASE_TO_UPPER=false
-</li>
-<li>Issue #1742, PR #1743: Assorted small changes
-</li>
-<li>PR #1738: Reduce memory allocation in getSQL() methods
-</li>
-<li>PR #1737: more javadoc updates
-</li>
-<li>Issue #1735: Creating views with DATABASE_TO_UPPER=FALSE fails
-</li>
-<li>Issue #1732: source.html does not work
-</li>
-<li>Issue #1730: Show error in H2 Console if specified driver is not compatible with URL
-</li>
-<li>Issue #1590: Error on executing "DELETE FROM table1 WHERE ID = ?; DELETE FROM table2 WHERE ID = ?;"
-</li>
-<li>Issue #1727: Support ISODOW as identifier for the extract function additional to ISO_DAY_OF_WEEK
-</li>
-<li>PR #1580, #1726: Disable remote database creation by default
-</li>
-<li>PR #1725: Add partial implementation of standard LISTAGG aggregate function
-</li>
-<li>PR #1722: Fix window definition lookup in some queries
-</li>
-<li>PR #1721: Fix derived column list in complex queries
-</li>
-<li>Issue #1718: Window function and values clause don't work well together
-</li>
-<li>Issue #1592: Index out of bounds exception in Page.getKey()
-</li>
-<li>PR #1716: Improve documentation of some DML commands
-</li>
-<li>Issue #1715: Postgres mode: Domain "regproc" already exists
-</li>
-<li>PR #1714: Assorted changes
-</li>
-<li>PR #1713: Remove DataType.defaultDisplaySize and fix display size in TypeInfo
-</li>
-<li>PR #1711: Add QUALIFY clause to SELECT command
-</li>
-<li>Issue #1708: CREATE TABLE AS doesn't support column lists without data types
-</li>
-<li>PR #1707: Fix sort order and ENUM data type in external results
-</li>
-<li>PR #1706: Add hypothetical set functions
-</li>
-<li>PR #1705: Fix GROUP_CONCAT with variable separator
-</li>
-<li>PR #1704: Fix return type of PERCENTILE_CONT and MEDIAN
-</li>
-<li>PR #1701: Add PERCENTILE_CONT and PERCENTILE_DISC inverse distribution functions
-</li>
-<li>Issues #1297, #1697: Failure on concurrent session closure
-</li>
-<li>Issue #1297: removeOldTempIndexes on PageStore causes NullPointerException
-</li>
-<li>Issue #1354: TestCrashAPI: another NPE
-</li>
-<li>PR #1695: Reduce memory for TestMVTempResult to 64m
-</li>
-<li>Issue #1691: Append mode causes OOME in MVPlainTempResult
-</li>
-<li>PR #1692: Use MVTempResult unconditionally
-</li>
-<li>Issue #1689: Use separate constants for data types in Data, ValueDataType, and Transfer
-</li>
-<li>PR #1687: MVMap minor cleanup
-</li>
-<li>PR #1686: Fix a regression with ENUM data type
-</li>
-<li>PR #1685: Fix CHAR in PostgreSQL mode and refactor some code
-</li>
-<li>Issue #1681: IN () doesn't work with row values when data types are not exactly the same
-</li>
-<li>Issue #1320: OOME / GC overhead in IndexCursor.nextCursor()
-</li>
-<li>PR #1680: Assorted fixes for ALTER TABLE ALTER COLUMN
-</li>
-<li>PR #1679: Use TestScript for testSimple
-</li>
-<li>Issue #1677: Unable to use VALUES keyword in WHERE clause
-</li>
-<li>Issue #1672: Deadlock on MVStore close in TestOutOfMemory
-</li>
-<li>Issue #1665: TestCrashAPI: NPE with ENUM in MINUS operator
-</li>
-<li>Issue #1602: Combine type, precision, scale, display size and extTypeInfo into one object
-</li>
-<li>PR #1671: Assorted changes
-</li>
-<li>Issue #1668: MySQL compatibility DATE() function should return NULL on error
-</li>
-<li>Issue #1604: TestCrashAPI: PreparedStatement.getGeneratedKeys() is already closed
-</li>
-<li>PR #1667: Detect NULL values and overflow in window frame bounds
-</li>
-<li>PR #1664: Allow any expressions in window frames
-</li>
-<li>Issue #1576: H2 Console should not display precision and scale for data types that don't have them
-</li>
-<li>PR #1662: Fix Alter Table Drop Column In View when table name is wrapped by Double Quotes
-</li>
-<li>PR #1660: Optimize window aggregates with AND UNBOUNDED FOLLOWING and no exclusions
-</li>
-<li>PR #1658: Assorted small changes
-</li>
-<li>PR #1657: Failure to stop background thread
-</li>
-<li>PR #1656: Optimize window aggregates with ORDER BY + UNBOUNDED PRECEDING + no exclusions
-</li>
-<li>Issue #1654: OOM in TestMemoryUsage, in big mode
-</li>
-<li>Issue #1651: TIMESTAMP values near DST may be changed in MVStore database due to UTC-based PageStore format in some
-temporary storages
-</li>
-<li>PR #1650: Fix race in MVStore.close()
-</li>
-<li>Issue #1212: TestDiskFull: The file is locked
-</li>
-<li>PR #1648: Add functions ARRAY_CAT(), ARRAY_APPEND() and ARRAY_SLICE()
-</li>
-<li>PR #1646: In preparation to a release
-</li>
-<li>PR #1643: more javadoc update
-</li>
-<li>PR #1642: update javadoc
-</li>
-<li>PR #1641: Update copyright years
-</li>
-<li>PR #1640: Suggest ANY(?) instead of variable IN() again
-</li>
-<li>PR #1638: Add support for Java 11 to test suite
-</li>
-<li>PR #1637: Remove explicit unboxing
-</li>
-<li>PR #1635: Optimize UUID to VARCHAR conversion and use correct time check in Engine.openSession()
-</li>
-<li>Issue #1632: TestMVTableEngine failure
-</li>
-<li>PR #1631: Prepare to release: javadoc cleanup
-</li>
-<li>PR #1630: fix duplicate words typos in comments and javadoc
-</li>
-<li>PR #1627: Use lock to protect append buffer
-</li>
-<li>Issue #1618: GROUP BY does not work with two identical columns in selected expressions
-</li>
-<li>Issue #1619: Two-phase commit regression in MASTER
-</li>
-<li>PR #1626: fix doc
-</li>
-<li>PR #1625: Prepare to release: javadoc cleanup, fix maven build, fix javadoc build
-</li>
-<li>Issue #1620: UUIDs are unexpectedly sorted as signed
-</li>
-<li>PR #1614: Use bulk .addAll() operation
-</li>
-<li>PR #1613: Add explicit table query
-</li>
-<li>Issue #1608: ARRAY and row value expression should not be the same
-</li>
-<li>Issue #1606: Quantified comparison predicate doesn't work correctly on primary key column
-</li>
-<li>Issue #1057: Very slow execution with subquery and connection parameter LAZY_QUERY_EXECUTION=1
-</li>
-<li>Issue #1072: Very slow execution with join and connection parameter LAZY_QUERY_EXECUTION=1
-</li>
-<li>PR #1601: Return BIGINT from ROWNUM(), ROW_NUMBER() and rank functions
-</li>
-<li>PR #1599: cleanup StringUtils.cache
-</li>
-<li>PR #1598: Minor changes in parser and documentation
-</li>
-<li>PR #1597: Remove SysProperties.CHECK preconditions around simple assertions
-</li>
-<li>PR #1596: Improve SQL Standard compliance in LOB precision parsing
-</li>
-<li>Issue #1594: DBSettings.optimizeIsNull and dead code in IndexCursor.getMax()
-</li>
-<li>PR #1591: Use multi-catch java 7 language construction to simplify code
-</li>
-<li>Issue #1582: h2 not using best index for >=
-</li>
-<li>PR #1588: Add support for java.time.Period
-</li>
-<li>Issue #446: FILE_READ from classpath not working because of 0 byte file length
-</li>
-<li>PR #1579: fix unintentional append mode disruption
-</li>
-<li>Issue #1573: DELETE FROM w/ ROWNUM and subquery
-</li>
-<li>Issue #187: SHUTDOWN DEFRAG corrupts splitted file database
-</li>
-<li>PR #1571: Optimizing ConditionAndOr queries
-</li>
-<li>Issue #1565: SOME / ANY conflict
-</li>
-<li>PR #1564: Refactor Expression implementations
-</li>
-<li>Issue #1561: Incorrect documentation and strange fallback value of SysProperties.FILE_ENCODING
-</li>
-<li>Issue #1566: MVStore implements Closeable/AutoCloseable
-</li>
-<li>Issue #1550: OutOfMemoryError during "shutdown defrag"
-</li>
-<li>Issue #1440: OOM when executing "shutdown compact" in server mode
-</li>
-<li>Issue #1561: Incorrect documentation and strange fallback value of SysProperties.FILE_ENCODING
-</li>
-<li>PR #1557: increase lock timeout to TestConcurrentUpdate due to Travis failures
-</li>
-<li>Issue #1554: REGEXP_REPLACE - accept 'g' flag in PostgreSQL compatibility mode
-</li>
-<li>Issue #950: Comparison between databases in README.md and in features.html
-</li>
-<li>Issue #1549: [RFE] Implement locking modes (select for update)
-</li>
-<li>PR #1548: Add AsynchronousFileChannel-based experimental FilePathAsync
-</li>
-<li>PR #1547: Speedup unused chunks collection
-</li>
-<li>PR #1546: Tiny optimization: use `System.arraycopy` when possible
-</li>
-<li>PR #1545: Export datetime value functions to SQL using standard syntax
-</li>
-<li>Issue #1371: NPE in CacheLRU
-</li>
-<li>Issue #1534: Typo in message
-</li>
-<li>Issue #1527: Parser performance: Excessive use of regular expressions to validate column names
-</li>
-<li>PR #1543: MVStore assorted re-factorings
-</li>
-<li>PR #1538: Add support for newer Lucene versions without recompilation
-</li>
-<li>Issue #1536: CURRENT_TIMESTAMP result doesn't change under Transactions
-</li>
-<li>Issue #239: Consider supporting Lucene 5 indexes
-</li>
-<li>PR #1520: Fixes bug in PutIfAbsentDecisionMaker
-</li>
-<li>Issue #1518: ENUM and VIEW with filtering on enum column
-</li>
-<li>Issue #1516: Array element reference array[index] should be 1-based
-</li>
-<li>Issue #1512: TestMVTableEngine.testLowRetentionTime(): NPE in VersionedValue.Type
-</li>
-<li>PR #1513: Assorted minor changes
-</li>
-<li>PR #1510: Add optional EXCEPT clause to wildcards
-</li>
-<li>PR #1509: Use domain term everywhere
-</li>
-<li>Issue #1507: Add INFORMATION_SCHEMA.COLUMNS.COLUMN_TYPE qualification for domains
-</li>
-<li>Issue #1499: TestScript::envelope.sql failure in “big” mode
-</li>
-<li>Issue #1498: NPE in SimpleResultSet.getColumnCount()
-</li>
-<li>Issue #1495: MERGE statement doesn't affect any rows when Oracle UPDATE .. WHERE .. DELETE .. WHERE is used
-</li>
-<li>Issue #1493: MERGE statement fails when it updates more than one row
-</li>
-<li>Issue #1492: Unnecessary restriction on MERGE USING statement when ON clause doesn't reference any target table columns
-</li>
-<li>Issue #1491: Unnecessary restriction on MERGE USING statement when ON predicate doesn't match inserted row
-</li>
-<li>Issue #1490: NullPointerException when running invalid MERGE statement
-</li>
-<li>Issue #1489: MERGE USING documentation has misleading railroad diagram
-</li>
-<li>Issue #1488: Improve documentation of window and some other functions
-</li>
-<li>Issue #1485: Default window frame in presence of ORDER BY is RANGE .., not ROWS
-</li>
-<li>PR #1484: New tests, reimplemented EXCLUDE clause, and assorted changes
-</li>
-<li>Issue #1338: MSSQLServer compatibility enhancements
-</li>
-<li>PR #1480: Update Maven build instruction and fix some problems
-</li>
-<li>PR #1478: Upgrade maven-surefire-plugin
-</li>
-<li>PR #1476: Add TransactionStore to MVStore jar
-</li>
-<li>Issue #1475: Dropping column used by a view produces misleading error message
-</li>
-<li>Issue #1473: TestScript needs better detection of sorted result
-</li>
-<li>PR #1471: issue 1350: TestCrashAPI: PageStore.freeListPagesPerList
-</li>
-<li>PR #1470: Fix window functions in queries with HAVING
-</li>
-<li>PR #1469: Forbid incorrect nesting of aggregates and window functions
-</li>
-<li>Issue #1437: Generated as Identity has a different behaviour.
-</li>
-<li>PR #1467: Fix subtraction of timestamps
-</li>
-<li>PR #1464: Assorted minor changes in window processing code
-</li>
-<li>PR #1463: Fix some window aggregates and reduce amount of collecting implementations
-</li>
-<li>PR #1462: Separate aggregate and window code in some places
-</li>
-<li>PR #1461: Add WINDOW clause support
-</li>
-<li>Issue #1427: Scalability problem in MVSpatialIndex
-</li>
-<li>PR #1459: Improve window clause correctness checks
-</li>
-<li>PR #1457: Add NTILE(), LEAD() and LAG() window functions
-</li>
-<li>PR #1456: Add experimental implementation of remaining types of window frames
-</li>
-<li>PR #1454: Add FIRST_VALUE(), LAST_VALUE(), and NTH_VALUE()
-</li>
-<li>PR #1453, Issue #1161: Add ROW_NUMBER(), RANK(), DENSE_RANK(), PERCENT_RANK(), and CUME_DIST() window functions
-</li>
-<li>PR #1452: Reset aggregates before reuse
-</li>
-<li>PR #1451: Add experimental support for aggregates with OVER (ORDER BY *)
-</li>
-<li>PR #1450: Evaluate window aggregates only once for each partition
-</li>
-<li>PR #1449: Move more code from Aggregate and JavaAggregate to AbstractAggregate
-</li>
-<li>PR #1448: Add experimental implementation of grouped window queries
-</li>
-<li>PR #1447: Refactor OVER() processing code and fix some issues
-</li>
-<li>PR #1446: fix : The French messages are bad generated (not contain DB message)
-</li>
-<li>PR #1445: Use PostGIS-compatible format for SRID-only constraint in GEOMETRY
-</li>
-<li>PR #1444: Add experimental unoptimized support for OVER ([PARTITION BY ...]) in aggregates
-</li>
-<li>PR #1442: Bugfix - Release MVStore lock and file resources rightly even if errors when compacting database
-</li>
-<li>PR #1441: Add GEOMETRY type subtypes with type and SRID constraints
-</li>
-<li>PR #1434: Add support for ENUM in CAST and other changes
-</li>
-<li>PR #1431: Fix some inconsistencies in documentation and improve mvn build
-</li>
-<li>PR #1428: Add support for M and ZM dimensions to GEOMETRY data type
-</li>
-<li>Issue #1405: Introduce LocalResult factory
-</li>
-<li>PR #1422: Add ENVELOPE aggregate function
-</li>
-<li>Issue #1421: Remove old-style outer join
-</li>
-<li>PR #1419: Assorted minor changes
-</li>
-<li>PR #1414: DEFRAG and COMPACT mixup
-</li>
-<li>PR #1413: improvements to MVStore garbage collection
-</li>
-<li>PR #1412: Added org.h2.store.fs package to exported osgi bundles
-</li>
-<li>PR #1409: Map all remaining error codes to custom exception classes
-</li>
-<li>Issue #1407: Add a MODE() aggregate function
-</li>
-<li>PR #1402: Duplicate conditions in column check constraint
-</li>
-<li>PR #1399: Add more subclasses of SQLException and use it for some error codes
-</li>
-<li>PR #1397: Add DATEADD return type detection
-</li>
-<li>Issue #1393: Add INFORMATION_SCHEMA.COLUMNS.IS_VISIBLE
-</li>
-<li>PR #1392: Some refactoring and assorted minor optimizations
-</li>
-<li>PR #1388: Extract UnaryOperation from Operation and other changes
-</li>
-<li>PR #1386: DISK_SPACE_USED() for MVStore and other minor changes
-</li>
-<li>PR #1385: split up the rather large convertTo method
-</li>
-<li>PR #1384: Throw exception if unknown mode is specified in database URL
-</li>
-<li>Issue #1365, PR #1382: Parse more date-time literals for compatibility with other databases
-</li>
-<li>PR #1381: Minor fixes for INTERVAL data type
-</li>
-<li>PR #1380: Improve documentation of intervals
-</li>
-<li>Issue #1189: "Merge into using" parameters aren't found
-</li>
-<li>Issue #1377: org.h2.api.Interval and TIME leftovers
-</li>
-<li>PR #1376: TestMultiThreadedKernel is back
-</li>
-<li>PR #1373: INTERVAL data type
-</li>
-<li>Issue #1369: In MSSQL Server Mode generated UUID fields need NEWID() function
-</li>
-<li>Issue #756: FunctionsMySql is not in the main jar
-</li>
-<li>PR #1368: Parse BINARY VARYING, BINARY LARGE OBJECT, and CHARACTER LARGE OBJECT
-</li>
-<li>PR #1367: Assorted changes with SELECT output limitation clauses
-</li>
-<li>Issue #1363: Why H2 requires random own packages in OSGi bundle description?
-</li>
-<li>Issue #1192: Add an Automatic-Module-Name
-</li>
-<li>Issue #1361, PR #1362: Add limited support for MONEY and SMALLMONEY in compatibility modes
-</li>
-<li>Issue #1327: mvn build misses some resources
-</li>
-<li>PR #1359: Add system property to return OffsetDateTime from ResultSet.getObject()
-</li>
-<li>PR #1357: Simplify execution flow in some places
-</li>
-<li>PR #1356: Fix NPE in Query.initExpression()
-</li>
-<li>PR #1355: Assorted changes in MetaTable
-</li>
-<li>Issue #1352: TestCrashAPI: Prepared.getObjectId() was called before
-</li>
-<li>PR #1349: Changes is conversion and comparison methods of Value
-</li>
-<li>Issue #1346: Exception when using IN condition for enums
-</li>
-<li>PR #1345: Replace some init methods with constructors
-</li>
-<li>PR #1344: Streamline last chunk verification on startup
-</li>
-<li>PR #1341: Optimize MVSecondaryIndex.convertToKey()
-</li>
-<li>PR #1340: NoSuchElementException instead of returning null
-</li>
-<li>PR #1339: Add support of TIMESTAMP WITH TIME ZONE to addition and subtraction operators
-</li>
-<li>PR #1337: Streamline Value comparison
-</li>
-<li>PR #1336: Minor refactorings
-</li>
-<li>Issue #1332: Constraint name not set correctly
-</li>
-<li>Rename fields to reflect actual type
-</li>
-<li>Issue #1331: Regression in Database.updateMeta()
-</li>
-<li>Issue #1323: Slow update after altering table in 1.4.197
-</li>
-<li>PR #1326: Add support of PERCENT in FETCH and TOP clauses
-</li>
-<li>PR #1325: Optimize WITH TIES in some queries and specify data types for KEY_COLUMN_USAGE
-</li>
-<li>PR #1321: Do not add rows before OFFSET to result if possible
-</li>
-<li>PR #1319: Treat NEXTVAL as an auto-generated key
-</li>
-<li>PR #1318: Mode append fo MVPlainTempResult
-</li>
-<li>PR #1314: Add ALTER VIEW RENAME command
-</li>
-<li>PR #1313, issue #1315: Bugfix - using default locale encoding issue in conversion between varchar and varbinary value, and checking javac output text issue in SourceCompiler
-</li>
-<li>PR #1312: Add Java 9+ support to NIO_CLEANER_HACK
-</li>
-<li>PR #1311: Fix minor issues with ResultSet.getObject(..., Class) and WITH TIES
-</li>
-<li>Issue #1298: TestKillRestartMulti: A map named undoLog.2 already exists
-</li>
-<li>Issue #1307: Invalid value "null" for parameter "calendar" [90008-193]
-</li>
-<li>PR #1306: Add initial implementation of WITH TIES clause
-</li>
-<li>PR #1304: Update changelog and fix building of documentation
-</li>
-<li>PR #1302: Use OpenJDK instead of OracleJDK 10 in Travis builds due to Travis problem
-</li>
-<li>Issue #1032: Error when executing "SELECT DISTINCT ON"
-</li>
-<li>Issue #1295: ConditionInSelect violates requirements of LocalResult
-</li>
-<li>PR #1296: Assorted minor changes
-</li>
-<li>PR #1293: Move HELP and SHOW tests into own files
-</li>
-<li>PR #1291: Fix update count for REPLACE and move some SQL tests into separate files
-</li>
-<li>PR #1290: Do not load the whole LOBs into memory for comparison operation
-</li>
-<li>Issue #408: DISTINCT does not properly work with ORDER BY on function like LOWER
-</li>
-<li>PR #1286: Fix MVTempResult implementations for results with invisible columns
-</li>
-<li>Issue #1284: Nanoseconds of timestamps from old H2 versions are not read properly
-</li>
-<li>PR #1283: Clean up interaction between LocalResult and ResultExternal
-</li>
-<li>Issue #1265: OOME is not handled properly in TraceObject.logAndConvert()
-</li>
-<li>Issue #1061: Regression: Braces after WITH clause not allowed anymore
-</li>
-<li>PR #1277: Assorted changes in Parser
-</li>
-<li>PR #1276: Improve support of ARRAY and SQLXML in JDBC layer
-</li>
-<li>PR #1275: Do not quote other lower case characters
-</li>
-<li>PR #1274: Use token type in Parser instead of string comparisons
-</li>
-<li>PR #1272: Reduce code duplication in Parser
-</li>
-<li>PR #1271: Minor memory leak
-</li>
-<li>PR #1270: drop TableView isPersistent field
-</li>
-<li>PR #1269: Eliminate commit of empty batch in some tests
-</li>
-<li>Issue #1266: Add INFORMATION_SCHEMA.COLUMNS.DATETIME_PRECISION
-</li>
-<li>Issue #1261: How to discover stored enum types through INFORMATION_SCHEMA
-</li>
-<li>Issue #1258: Failing to remove index when using schema.table
-</li>
-<li>PR #1256: misc tiny refactorings
-</li>
-<li>PR #1255: Minor changes in MERGE USING, DATE_TRUNC, and EXTRACT
-</li>
-<li>Issue #1214: Internal compiler believes that "3 warnings" is an error
-</li>
-<li>PR #1252: Assorted minor changes
-</li>
-<li>PR #1251: Fix SQL representation of CAST for types with fractional seconds precision
-</li>
-<li>PR #1250: Batch append mode for MVMap
-</li>
-<li>PR #1248: StringIndexOutOfBoundsException due to undoLog map
-</li>
-<li>PR #1246: Detect disabled tests
-</li>
-<li>PR #1242: Add implementation of SQLXML interface
-</li>
-<li>PR #1241: Various tweaks in attempting to fix TestDiskFull test
-</li>
-<li>PR #1240: Optimise ValueLobDB comparison methods
-</li>
-<li>PR #1239: Don't try to find tools.jar on Java 9+
-</li>
-<li>PR #1238: remove unfinished android API
-</li>
-<li>PR #1237: remove JaQu
-</li>
-<li>PR #1236: remove STORE_LOCAL_TIME code
-</li>
-<li>PR #1235: Do not use deprecated Class.newInstance()
-</li>
-<li>PR #1234: Fix NPE in Parser.parseMergeUsing()
-</li>
-<li>PR #1233: Simplify old lob ValueLob class
-</li>
-<li>Issue 1227: lob growth in pagestore mode
-</li>
-<li>PR #1230: clean up some javadoc and some throws clauses
-</li>
-<li>PR #1229: Create UndoLog only when necessary and remove outdated code
-</li>
-<li>PR #1228: Remove some PageStore+MVCC leftovers
-</li>
-<li>PR #1226: Fix inconsistencies in checks for transaction isolation level
-</li>
-<li>PR #1224: Enable Java 10 testing on Travis
-</li>
-<li>PR #1223: Fix issues with testing on latest Java versions
-</li>
-<li>PR #1222: Leftovers handling
-</li>
-<li>Issue #1220: JDK-9 build fails due to usage of java.xml.bind in external authentication
-</li>
-<li>PR #1218: Test utilities only once during TestAll
-</li>
-<li>PR #1217: Postpone session.endStatement() until after commit
-</li>
-<li>PR #1213: KillRestart fix
-</li>
-<li>PR #1211: Assorted minor changes
-</li>
-<li>Issue #1204: Always use MVCC with MVStore and never use it with PageStore
-</li>
-<li>PR #1206: Forbid reconnects in non-regular modes in TestScript
-</li>
-<li>PR #1205: Misc test fixes
-</li>
-<li>Issue 1198: Enable MULTI_THREADED by default for MVStore mode
-</li>
-<li>Issue #1195: Calling setBytes to set VARCHAR field fails
-</li>
-<li>PR #1197: Fix or suppress errors in tests
-</li>
-<li>PR #1194: TestKillRestartMulti: A map named undoLog-1 already exists
-</li>
-<li>PR #1193: enable TestRandomSQL on non-memory databases
-</li>
-<li>PR #1191: External authentication with datasource issue
-</li>
-<li>PR #1188: Undo log split to reduce contention
-</li>
-<li>PR #1186: TransactionMap::sizeAsLong() optimized - temp map eliminated
-</li>
-<li>PR #1185: Improve naming of the object id field in Prepared
-</li>
-<li>Issue #1196: Feature request for MS SQL Server Compatibility Mode
-</li>
-<li>Issue #1177: Resource leak in Recover tool
-</li>
-<li>PR #1183: Improve concurrency of connection pool with wait-free implement
-</li>
-<li>Issue #1073: H2 v1.4.197 fails to open an existing database with the error [Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"]
-</li>
-<li>PR #1179: Drop TransactionMap.readLogId
-</li>
-<li>PR #1181: Improve CURRENT_TIMESTAMP and add LOCALTIME and LOCALTIMESTAMP
-</li>
-<li>PR #1176: Magic value replacement with constant
-</li>
-<li>PR #1171: Introduce last committed value into a VersionedValue
-</li>
-<li>PR #1175: tighten test conditions - do not ignore any exceptions
-</li>
-<li>PR #1174: Remove mapid
-</li>
-<li>PR #1173: protect first background exception encountered and relate it to clients
-</li>
-<li>PR #1172: Yet another attempt to tighten that testing loop
-</li>
-<li>PR #1170: Add support of CONTINUE | RESTART IDENTITY to TRUNCATE TABLE
-</li>
-<li>Issue #1168: ARRAY_CONTAINS() returning incorrect results when inside subquery with Long elements.
-</li>
-<li>PR #1167: MVStore: Undo log synchronization removal
-</li>
-<li>PR #1166: Add SRID support to EWKT format
-</li>
-<li>PR #1165: Optimize isTargetRowFound() and buildColumnListFromOnCondition() in MergeUsing
-</li>
-<li>PR #1164: More fixes for parsing of MERGE USING and other changes in Parser
-</li>
-<li>PR #1154: Support for external authentication
-</li>
-<li>PR #1162: Reduce allocation of temporary strings
-</li>
-<li>PR #1158: make fields final
-</li>
-<li>Issue #1129: TestCrashAPI / TestFuzzOptimizations throw OOME on Travis in PageStore mode
-</li>
-<li>PR #1156: Add support for SQL:2003 WITH [NO] DATA to CREATE TABLE AS
-</li>
-<li>PR #1149: fix deadlock between OnExitDatabaseCloser.DATABASES and Engine.DATABASES
-</li>
-<li>PR #1152: skip intermediate DbException object when creating SQLException
-</li>
-<li>PR #1144: Add missing schema name with recursive view
-</li>
-<li>Issue #1091: get rid of the "New" class
-</li>
-<li>PR #1147: Assorted minor optimizations
-</li>
-<li>PR #1145: Reduce code duplication
-</li>
-<li>PR #1142: Misc small fixes
-</li>
-<li>PR #1141: Assorted optimizations and fixes
-</li>
-<li>PR #1138, #1139: Fix a memory leak caused by DatabaseCloser objects
-</li>
-<li>PR #1137: Step toward making transaction commit atomic
-</li>
-<li>PR #1136: Assorted minor optimizations
-</li>
-<li>PR #1134: Detect possible overflow in integer division and optimize some code
-</li>
-<li>PR #1133: Implement Comparable<Value> in CompareMode and optimize ValueHashMap.keys()
-</li>
-<li>PR #1132: Reduce allocation of ExpressionVisitor instances
-</li>
-<li>PR #1130: Improve TestScript and TestCrashAPI
-</li>
-<li>PR #1128: Fix ON DUPLICATE KEY UPDATE with ENUM
-</li>
-<li>PR #1127: Update JdbcDatabaseMetaData.getSQLKeywords() and perform some minor optimizations
-</li>
-<li>PR #1126: Fix an issue with code coverage and building of documentation
-</li>
-<li>PR #1123: Fix TCP version check
-</li>
-<li>PR #1122: Assorted changes
-</li>
-<li>PR #1121: Add some protection to ValueHashMap against hashes with the same less significant bits
-</li>
-<li>Issue #1097: H2 10x slower than HSQLDB and 6x than Apache Derby for specific query with GROUP BY and DISTINCT subquery
-</li>
-<li>Issue #1093: Use temporary files for ResultSet buffer tables in MVStore
-</li>
-<li>PR #1117: Fix sorting with distinct in ResultTempTable
-</li>
-<li>Issue #1095: Add support for INSERT IGNORE INTO <table> (<columns>) SELECT in MySQL Mode
-</li>
-<li>PR #1114: Minor cleanup and formatting fixes
-</li>
-<li>PR #1112: Improve test scripts
-</li>
-<li>PR #1111: Use a better fix for issue with SRID
-</li>
-<li>Issue #1107: Restore support of DATETIME2 with specified fractional seconds precision
-</li>
-<li>Issue #1106: Get rid of SwitchSource
-</li>
-<li>PR #1105: Assorted minor changes
-</li>
-<li>Issue #1102: CREATE SYNONYM rejects valid definition
-</li>
-<li>PR #1103: Remove redundant synchronization
-</li>
-<li>Issue #1048: 1.4.197 regression. org.h2.jdbc.JdbcSQLException: Timeout trying to lock table "SYS"
-</li>
-<li>PR #1101: Move some tests in better place and add an additional test for 2PC
-</li>
-<li>PR #1100: Fix Insert.prepareUpdateCondition() for PageStore
-</li>
-<li>PR #1098: Fix some issues with NULLS FIRST / LAST
-</li>
-<li>Issue #1089: Parser does not quote words INTERSECTS, DUAL, TOP
-</li>
-<li>Issue #230: Renaming a column does not update foreign key constraint
-</li>
-<li>Issue #1091 Get rid if the New class
-</li>
-<li>PR #1087: improve performance of planning large queries
-</li>
-<li>PR #1085: Add tests for simple one-column index sorting
-</li>
-<li>PR #1084: re-enable some pagestore testing
-</li>
-<li>PR #1083: Assorted changes
-</li>
-<li>Issue #394: Recover tool places COLLATION and BINARY_COLLATION after temporary tables
-</li>
-<li>PR #1081: Session.getTransactionId should return a more distinguishing value
-</li>
-<li>Improve the script-based unit testing to check the error code of the exception thrown.
-</li>
-<li>Issue #1041: Support OR syntax while creating trigger
-</li>
-<li>Issue #1023: MVCC and existing page store file
-</li>
-<li>Issue #1003: Decrypting database with incorrect password renders the database corrupt
-</li>
-<li>Issue #873: No error when `=` in equal condition when column is not of array type
-</li>
-<li>Issue #1069: Failed to add DATETIME(3) column since 1.4.197
-</li>
-<li>Issue #456: H2 table privileges referring to old schema after schema rename
-</li>
-<li>Issue #1062: Concurrent update in table "SYS" caused by Analyze.analyzeTable()
-</li>
-<li>Yet another fix to Page memory accounting
-</li>
-<li>Replace MVStore.ASSERT variable with assertions
-</li>
-<li>Issue #1063: Leftover comments about enhanced for loops
-</li>
-<li>PR #1059: Assorted minor changes
-</li>
-<li>PR #1058: Txcommit atomic
-</li>
-<li>Issue #1038: ora_hash function implementation off by one
-</li>
-<li>PR #1054: Introduce overflow bit in tx state
-</li>
-<li>Issue #1047: Support DISTINCT in custom aggregate functions
-</li>
-<li>PR #1051: Atomic change of transaction state
-</li>
-<li>PR #1046: Split off Transaction TransactionMap VersionedValue
-</li>
-<li>PR #1045: TransactionStore move into separate org.h2.mvstore.tx package
-</li>
-<li>PR #1044: Encapsulate TransactionStore.store field in preparation to a move
-</li>
-<li>PR #1040: generate less garbage for String substring+trim
-</li>
-<li>PR #1035: Minor free space accounting changes
-</li>
-<li>Issue #1034: MERGE USING should not require the same column count in tables
-</li>
-<li>PR #1033: Fix issues with BUILTIN_ALIAS_OVERRIDE=1
-</li>
-<li>PR #1031: Drop schema rights together with schema
-</li>
-<li>PR #1029: No need to remove orphaned LOBs when the db is read-only
-</li>
-<li>Issue #1027: Add support for fully qualified names in MySQL compatibility mode
-</li>
-<li>Issue #178: INSERT ON DUPLICATE KEY UPDATE returns wrong generated key
-</li>
-<li>PR #1025: Remove BitField and replace its usages with BitSet
-</li>
-<li>Issue #1019: Console incorrectly sorts BigDecimal columns alphanumerically
-</li>
-<li>PR #1021: Update JdbcDatabaseMetaData to JDBC 4.1 (Java 7)
-</li>
-<li>Issue #992: 1.4.197 client cannot use DatabaseMetaData with 1.4.196 and older server
-</li>
-<li>Issue #1016: ResultSet.getObject() should return enum value, not ordinal
-</li>
-<li>Issue #1012: NPE when querying INFORMATION_SCHEMA.COLUMNS on a view that references an ENUM column
-</li>
-<li>Issue #1010: MERGE USING table not found with qualified table
-</li>
-<li>PR #1009: Fix ARRAY_AGG with ORDER BY and refactor aggregates
-</li>
-<li>Issue #1006: "Empty enums are not allowed" in 1.4.197 (mode=MYSQL)
-</li>
-<li>PR #1007: Copy also SRID in ValueGeometry.getGeometry()
-</li>
-<li>PR #1004: Preserve type names in more places especially for UUID
-</li>
-<li>Issue #1000: Regression in INFORMATION_SCHEMA.CONSTRAINTS.CONSTRAINT_TYPE content
-</li>
-<li>Issue #997: Can not delete from tables with enums
-</li>
-<li>Issue #994: Too much column in result set for GENERATED_KEYS on table with DEFAULT
-</li>
-<li>PR #993: Fix some compiler warnings and improve assert*() methods
-</li>
-<li>PR #991: Generate shorter queries in JdbcDatabaseMetaData.getTables() and remove some dead code
-</li>
-<li>PR #989: Fix more issues with range table and improve its documentation
-</li>
-</ul>
-
-<h2>Version 1.4.197 (2018-03-18)</h2>
-<ul>
-<li>PR #988: Fix RangeTable.getRowCount() for non-default step
-</li>
-<li>PR #987: ValueBoolean constants are not cleared and may be used directly
-</li>
-<li>PR #986: Check parameters in JdbcPreparedStatement.addBatch()
-</li>
-<li>PR #984: Minor refactorings in Parser
-</li>
-<li>PR #983: Code cleanups via IntelliJ IDEA inspections
-</li>
-<li>Issue #960: Implement remaining time unit in "date_trunc" function
-</li>
-<li>Issue #933: MVStore background writer endless loop
-</li>
-<li>PR #981: Reorganize date-time functions
-</li>
-<li>PR #980: Add Parser.toString() method for improved debugging experience
-</li>
-<li>PR #979: Remove support of TCP protocol versions 6 and 7
-</li>
-<li>PR #977: Add database versions to javadoc of TCP protocol versions and update dictionary.txt
-</li>
-<li>PR #976: Add and use incrementDateValue() and decrementDateValue()
-</li>
-<li>Issue #974: Inline PRIMARY KEY definition loses its name
-</li>
-<li>PR #972: Add META-INF/versions to all non-Android jars that use Bits
-</li>
-<li>PR #971: Update ASM from 6.1-beta to 6.1
-</li>
-<li>PR #970: Added support for ENUM in prepared statement where clause
-</li>
-<li>PR #968: Assorted changes
-</li>
-<li>PR #967: Adds ARRAY_AGG function
-</li>
-<li>PR #966: Do not include help and images in client jar
-</li>
-<li>PR #965: Do not include mvstore.DataUtils in client jar and other changes
-</li>
-<li>PR #964: Fix TestFunctions.testToCharFromDateTime()
-</li>
-<li>PR #963 / Issue #962: Improve documentation of compatibility modes and fix ssl URL description
-</li>
-<li>Issue #219: H2 mode MySQL- ON UPDATE CURRENT_TIMESTAMP not supported
-</li>
-<li>PR #958: More fixes for PgServer
-</li>
-<li>PR #957: Update database size information and links in README.md
-</li>
-<li>PR #956: Move tests added in 821117f1db120a265647a063dca13ab5bee98efc to a proper place
-</li>
-<li>PR #955: Support getObject(?, Class) in generated keys
-</li>
-<li>PR #954: Avoid incorrect reads in iterators of TransactionMap
-</li>
-<li>PR #952: Optimize arguments for MVMap.init()
-</li>
-<li>PR #949: Fix table borders in PDF and other changes
-</li>
-<li>PR #948: Fix some grammar descriptions and ALTER TABLE DROP COLUMN parsing
-</li>
-<li>PR #947: Fix building of documentation and use modern names of Java versions
-</li>
-<li>PR #943: Assorted changes in documentation and a fix for current-time.sql
-</li>
-<li>PR #942: Fix page numbers in TOC in PDF and move System Tables into own HTML / section in PDF
-</li>
-<li>PR #941: Use >> syntax in median.sql and move out more tests from testScript.sql
-</li>
-<li>PR #940: add Support for MySQL: DROP INDEX index_name ON tbl_name
-</li>
-<li>PR #939: Short syntax for SQL tests
-</li>
-<li>Issue #935: The "date_trunc" function is not recognized for 'day'
-</li>
-<li>PR #936: Fix font size, line length, TOC, and many broken links in PDF
-</li>
-<li>PR #931: Assorted changes in documentation
-</li>
-<li>PR #930: Use Math.log10() and remove Mode.getOracle()
-</li>
-<li>PR #929: Remove Mode.supportOffsetFetch
-</li>
-<li>PR #928: Show information about office configuration instead of fallback PDF generation mode
-</li>
-<li>PR #926: Describe datetime fields in documentation
-</li>
-<li>PR #925: Fix time overflow in DATEADD
-</li>
-<li>Issue #416: Add support for DROP SCHEMA x { RESTRICT | CASCADE }
-</li>
-<li>PR #922: Parse and treat fractional seconds precision as described in SQL standard
-</li>
-<li>Issue #919: Add support for mixing adding constraints and columns in multi-add ALTER TABLE statement
-</li>
-<li>PR #916: Implement TABLE_CONSTRAINTS and REFERENTIAL_CONSTRAINTS from the SQL standard
-</li>
-<li>PR #915: Implement INFORMATION_SCHEMA.KEY_COLUMN_USAGE from SQL standard
-</li>
-<li>PR #914: don't allow null values in ConcurrentArrayList
-</li>
-<li>PR #913: Assorted changes in tests and documentation
-</li>
-<li>Issue #755: Missing FLOAT(precision)?
-</li>
-<li>PR #911: Add support for MySQL-style ALTER TABLE ADD ... FIRST
-</li>
-<li>Issue #409: Support derived column list syntax on table alias
-</li>
-<li>PR #908: remove dead code
-</li>
-<li>PR #907: Nest joins only if required and fix some issues with complex joins
-</li>
-<li>PR #906: Fix obscure error on non-standard SELECT * FROM A LEFT JOIN B NATURAL JOIN C
-</li>
-<li>PR #805: Move some JOIN tests from testScript.sql to own file
-</li>
-<li>PR #804: Remove unused parameters from readJoin() and readTableFilter()
-</li>
-<li>Issue #322: CSVREAD WHERE clause containing ORs duplicates number of rows
-</li>
-<li>PR #902: Remove DbSettings.nestedJoins
-</li>
-<li>PR #900: Convert duplicate anonymous classes in TableFilter to nested for reuse
-</li>
-<li>PR #899: Fix ON DUPLICATE KEY UPDATE for inserts with multiple rows
-</li>
-<li>PR #898: Parse TIME WITHOUT TIME ZONE and fix TIMESTAMP as column name
-</li>
-<li>PR #897: Update JTS to version 1.15.0 from LocationTech
-</li>
-<li>PR #896: Assorted changes in help.csv
-</li>
-<li>PR #895: Parse more variants of timestamps with time zones
-</li>
-<li>PR #893: TIMESTAMP WITHOUT TIME ZONE, TIMEZONE_HOUR, and TIMEZONE_MINUTE
-</li>
-<li>PR #892: Assorted minor changes in Parser
-</li>
-<li>PR #891: Update documentation of date-time types and clean up related code a bit
-</li>
-<li>PR #890: Implement conversions for TIMESTAMP WITH TIME ZONE
-</li>
-<li>PR #888: Fix two-phase commit in MVStore
-</li>
-<li>Issue #884: Wrong test Resources path in pom.xml
-</li>
-<li>PR #886: Fix building of documentation
-</li>
-<li>PR #883: Add support for TIMESTAMP WITH TIME ZONE to FORMATDATETIME
-</li>
-<li>PR #881: Reimplement dateValueFromDate() and nanosFromDate() without a Calendar
-</li>
-<li>PR #880: Assorted date-time related changes
-</li>
-<li>PR #879: Reimplement TO_DATE without a Calendar and fix a lot of bugs an incompatibilities
-</li>
-<li>PR #878: Fix IYYY in TO_CHAR and reimplement TRUNCATE without a Calendar
-</li>
-<li>PR #877: Reimplement TO_CHAR without a Calendar and fix 12 AM / 12 PM in it
-</li>
-<li>PR #876: Test out of memory
-</li>
-<li>PR #875: Improve date-time related parts of documentation
-</li>
-<li>PR #872: Assorted date-time related changes
-</li>
-<li>PR #871: Fix OOME in Transfer.readValue() with large CLOB V2
-</li>
-<li>PR #867: TestOutOfMemory stability
-</li>
-<li>Issue #834: Add support for the SQL standard FILTER clause on aggregate functions
-</li>
-<li>PR #864: Minor changes in DateUtils and Function
-</li>
-<li>PR #863: Polish: use isEmpty() to check whether the collection is empty or not.
-</li>
-<li>PR #862: Convert constraint type into enum
-</li>
-<li>PR #861: Avoid resource leak
-</li>
-<li>PR #860: IndexCursor inList
-</li>
-<li>PR #858 / Issue #690 and others: Return all generated rows and columns from getGeneratedKeys()
-</li>
-<li>Make the JDBC client independent of the database engine
-</li>
-<li>PR #857: Do not write each SQL error multiple times in TestScript
-</li>
-<li>PR #856: Fix TestDateTimeUtils.testDayOfWeek() and example with ANY(?
-</li>
-<li>PR #855: Reimplement DATEADD without a Calendar and fix some incompatibilities
-</li>
-<li>PR #854: Improve test stability
-</li>
-<li>PR #851: Reimplement DATEDIFF without a Calendar
-</li>
-<li>Issue #502: SQL "= ANY (?)" supported?
-</li>
-<li>PR #849: Encode date and time in fast and proper way in PgServerThread
-</li>
-<li>PR #847: Reimplement remaining parts of EXTRACT, ISO_YEAR, etc without a Calendar
-</li>
-<li>PR #846: Read known fields directly in DateTimeUtils.getDatePart()
-</li>
-<li>Issue #832: Extract EPOCH from a timestamp
-</li>
-<li>PR #844: Add simple implementations of isWrapperFor() and unwrap() to JdbcDataSource
-</li>
-<li>PR #843: Add MEDIAN to help.csv and fix building of documentation
-</li>
-<li>PR #841: Support indexes with nulls last for MEDIAN aggregate
-</li>
-<li>PR #840: Add MEDIAN aggregate
-</li>
-<li>PR #839: TestTools should not leave testing thread in interrupted state
-</li>
-<li>PR #838: (tests) Excessive calls to Runtime.getRuntime().gc() cause OOM for no reason
-</li>
-<li>Don't use substring when doing StringBuffer#append
-</li>
-<li>PR #837: Use StringUtils.replaceAll() in Function.replace()
-</li>
-<li>PR #836: Allow to read invalid February 29 dates with LocalDate as March 1
-</li>
-<li>PR #835: Inline getTimeTry() into DateTimeUtils.getMillis()
-</li>
-<li>PR #827: Use dateValueFromDate() and nanosFromDate() in parseTimestamp()
-</li>
-<li>Issue #115: to_char fails with pattern FM0D099
-</li>
-<li>PR #825: Merge code for parsing and formatting timestamp values
-</li>
-<li>Enums for ConstraintActionType, UnionType, and OpType
-</li>
-<li>PR 824: Add partial support for INSERT IGNORE in MySQL mode
-</li>
-<li>PR #823: Use ValueByte.getInt() and ValueShort.getInt() in convertTo()
-</li>
-<li>PR #820: Fix some compiler warnings
-</li>
-<li>PR #818: Fixes for remaining issues with boolean parameters
-</li>
-<li>Use enum for file lock method
-</li>
-<li>PR #817: Parse also 1 as true and 0 as false in Utils.parseBoolean()
-</li>
-<li>PR #815: Fix count of completed statements
-</li>
-<li>PR #814: Method.isVarArgs() is available on all supported platforms
-</li>
-<li>Issue #812: TIME values should be in range 0:00:00.000000000 23:59:59.999999999?
-</li>
-<li>PR #811: Issues with Boolean.parseBoolean()
-</li>
-<li>PR #809: Use type constants from LocalDateTimeUtils directly
-</li>
-<li>PR #808: Use HmacSHA256 provided by JRE
-</li>
-<li>PR #807: Use SHA-256 provided by JRE / Android and use rotateLeft / Right in Fog
-</li>
-<li>PR #806: Implement setBytes() and setString() with offset and len
-</li>
-<li>PR #805: Improve support of TIMESTAMP WITH TIME ZONE
-</li>
-<li>PR #803: Use new ArrayList(Collection) and assertThrows()
-</li>
-<li>PR #802: Use Arrays.copyOf() and Arrays.copyOfRange()
-</li>
-<li>PR #801: Fix NULL support in PgServer for primitive types too
-</li>
-<li>PR #800: More fixes in date-time types for ODBC drivers
-</li>
-<li>PR #798: Add partial support of DATE, TIME, and TIMESTAMP data types to PgServer
-</li>
-<li>PR #799: Use result of ArrayList.remove()
-</li>
-<li>PR #797: Add ceilingKey() and floorKey() to TransactionMap (version 2)
-</li>
-<li>PR #796: Add MDY to DateStyle in PgServerThread
-</li>
-<li>PR #794: Sort files in generated jars
-</li>
-<li>PR #793: Change return type of Value.getBoolean() to boolean (unwrapped)
-</li>
-<li>PR #792: Inherit classpath from parent process
-</li>
-<li>PR #791: Switch to JaCoCo code coverage
-</li>
-<li>PR #788: Update lists of keywords
-</li>
-<li>PR #789: Map DATE in Oracle mode to ValueTimestamp
-</li>
-<li>PR #787: Assorted changes
-</li>
-<li>PR #785: Optimize NULL handling in MVSecondaryIndex.add()
-</li>
-<li>PR #783: Add Bits implementation for Java 9 and later versions
-</li>
-<li>PR #784: Hardcoded port numbers should not be used in unit tests
-</li>
-<li>PR #780: Close JavaFileManager after use.
-</li>
-<li>PR #782: Leftover shared lock after release
-</li>
-<li>PR #781: Locks left behind after commit
-</li>
-<li>PR #778: Reduce code duplication
-</li>
-<li>PR #775: Fix building of documentation and zip
-</li>
-<li>PR #774: Assorted changes
-</li>
-<li>PR #773: Better checks for arguments of partial LOB reading methods
-</li>
-<li>PR #772: getBinaryStream() and getCharacterStream() with pos and length
-</li>
-<li>Issue #754: Make NUMERIC type read as NUMERIC
-</li>
-<li>PR #768: Add DataUtils.parseChecksummedMap()
-</li>
-<li>PR #769: Do not copy result of DataUtils.parseMap() to a new maps
-</li>
-<li>PR #766: Minor clean up of DateTimeUtils
-</li>
-<li>PR #764: Make use of try-with-resources statement
-</li>
-<li>Issue #406: Return from ResultSet.getObject not in line with JDBC specification
-</li>
-<li>Issue #710: Misleading exception message when INSERT has no value for self referential 'AS' column
-</li>
-<li>PR #763: Add DataUtils.getMapName()
-</li>
-<li>PR #762: Add row deletion confirmation to web console
-</li>
-<li>PR #760: Assorted minor optimizations
-</li>
-<li>PR #759: Improve the look of error messages in web console
-</li>
-<li>PR #758: Allocate less amount of garbage
-</li>
-<li>PR #757: Fix handling of UUID in Datatype.readValue()
-</li>
-<li>PR #753: Optimize StringUtils.trim() and remove StringUtils.equals()
-</li>
-<li>PR #752: Use predefined charsets instead of names where possible
-</li>
-<li>PR #750: Use AtomicIntegerArray and StandardCharsets
-</li>
-<li>PR #749: Fix some build checks in sources
-</li>
-<li>Issue #740: TestWeb hangups if webSSL=true specified in configuration
-</li>
-<li>Issue #736: Copyright years in sources
-</li>
-<li>Issue #744: TestFile failure on Java 9 and Java 10
-</li>
-<li>PR #741: More cleanups in LocalDateTimeUtils and other minor changes
-</li>
-<li>PR #743: Change REGEXP_REPLACE mode for MariaDB and PostgreSQL
-</li>
-<li>Issue#646 NPE in CREATE VIEW WITH RECURSIVE & NON_RECURSIVE CTE
-</li>
-<li>PR #738: Copy javadoc to *BackwardsCompat to fix building of documentation
-</li>
-<li>PR #735: Add support of java.time.Instant V2
-</li>
-<li>PR #733: Remove JPA/ORM configuration txt files as they're already integrated
-</li>
-<li>PR #732: Fix ==
-</li>
-<li>PR #730: Implement enquoteIdentifier() and isSimpleIdentifier() from JDBC 4.3
-</li>
-<li>PR #729: Grammar documentation change
-</li>
-<li>PR #727: Integer/Long.compare(x, y) can be used to compare primitive values
-</li>
-<li>PR #726: Fixes in tests
-</li>
-<li>Issue #725: FilePathMem.tryLock() fails since Java 9
-</li>
-<li>PR #723: Clean up LocalDateTimeUtils
-</li>
-<li>PR #724: Use StringBuilder instead of StringBuffer
-</li>
-<li>PR #720: DROP TABLE RESTRICT shouldn't drop foreign keys in other tables
-</li>
-<li>PR #722: Assorted minor changes
-</li>
-<li>Issue #638: Oracle mode: incompatible regexp back-reference syntax
-</li>
-<li>Make ALL a reserved keyword
-</li>
-<li>Issue #311: Avoid calling list.toArray(new X[list.size()]) for performance
-</li>
-<li>PR #715: Better getObject error message
-</li>
-<li>PR #714: SecureRandom is already synchronized
-</li>
-<li>PR #712: Return properly encoded UUID from SimpleResultSet.getBytes()
-</li>
-<li>PR #711: TestFunctions less english dependent
-</li>
-<li>Issue #644: Year changing from negative -509 to a positive 510.
-</li>
-<li>PR #706: SIGNAL function
-</li>
-<li>PR #704: added Javascript support for Triggers' source
-</li>
-<li>Issue #694: Oracle syntax for adding NOT NULL constraint not supported.
-</li>
-<li>Issue #699: When using an index for sorting, the index is ignored when also using NULLS LAST/FIRST
-</li>
-<li>Issue #697: FilePathDisk.newInputStream fails for contextual class loading
-</li>
-<li>Issue #695: jdbc:postgresql protocol connection issue in H2 Console Application in case of redshift driver in classpath
-</li>
-<li>Fix 'file not closed' when using FILE_READ
-</li>
-<li>Fix bug in LinkSchema tool when object exists with same name in different schemas
-</li>
-<li>Issue #675: Fix date operations on Locales with non-Gregorian calendars
-</li>
-<li>Fix removal of LOB when rolling back transaction on a table containing more than one LOB column.
-</li>
-<li>Issue #654: List ENUM type values in INFORMATION_SCHEMA.COLUMNS
-</li>
-<li>Issue #650: Simple nested SELECT causes error for table with TIMESTAMP WITH TIMEZONE column
-</li>
-<li>Issue #654: List ENUM type values in INFORMATION_SCHEMA.COLUMNS
-</li>
-<li>Issue #668: Fail of an update command on large table with ENUM column
-</li>
-<li>Issue #662: column called CONSTRAINT is not properly escaped when storing to metadata
-</li>
-<li>Issue #660: Outdated java version mentioned on http://h2database.com/html/build.html#providing_patches
-</li>
-<li>Issue #643: H2 doesn't use index when I use IN and EQUAL in one query
-</li>
-<li>Reset transaction start timestamp on ROLLBACK
-</li>
-<li>Issue #632: CREATE OR REPLACE VIEW creates incorrect columns names
-</li>
-<li>Issue #630: Integer overflow in CacheLRU can cause unrestricted cache growth
-</li>
-<li>Issue #497: Fix TO_DATE in cases of 'inline' text. E.g. the "T" and "Z" in to_date('2017-04-21T00:00:00Z', 'YYYY-MM-DD"T"HH24:MI:SS"Z"')
-</li>
-<li>Fix bug in MySQL/ORACLE-syntax silently corrupting the modified column in cases of setting the 'NULL'- or 'NOT NULL'-constraint. E.g. alter table T modify C NULL;
-</li>
-<li>Issue #570: MySQL compatibility for ALTER TABLE .. DROP INDEX
-</li>
-<li>Issue #537: Include the COLUMN name in message "Numeric value out of range"
-</li>
-<li>Issue #600: ROW_NUMBER() behaviour change in H2 1.4.195
-</li>
-<li>Fix a bunch of race conditions found by vmlens.com, thank you to vmlens for giving us a license.
-</li>
-<li>PR #597: Support more types in getObject
-</li>
-<li>Issue #591: Generated SQL from WITH-CTEs does not include a table identifier
-</li>
-<li>PR #593: Make it possible to create a cluster without using temporary files.
-</li>
-<li>PR #592: "Connection is broken: "unexpected status 16777216" [90067-192]" message when using older h2 releases as client
-</li>
-<li>Issue #585: MySQL mode DELETE statements compatibility
-</li>
-<li>PR #586: remove extra tx preparation
-</li>
-<li>PR #568: Implement MetaData.getColumns() for synonyms.
-</li>
-<li>Issue #581: org.h2.tools.RunScript assumes -script parameter is part of protocol
-</li>
-<li>Fix a deadlock in the TransactionStore
-</li>
-<li>PR #579: Disallow BLOB type in PostgreSQL mode
-</li>
-<li>Issue #576: Common Table Expression (CTE): WITH supports INSERT, UPDATE, MERGE, DELETE, CREATE TABLE ...
-</li>
-<li>Issue #493: Query with distinct/limit/offset subquery returns unexpected rows
-</li>
-<li>Issue #575: Support for full text search in multithreaded mode
-</li>
-<li>Issue #569: ClassCastException when filtering on ENUM value in WHERE clause
-</li>
-<li>Issue #539: Allow override of builtin functions/aliases
-</li>
-<li>Issue #535: Allow explicit paths on Windows without drive letter
-</li>
-<li>Issue #549: Removed UNION ALL requirements for CTE
-</li>
-<li>Issue #548: Table synonym support
-</li>
-<li>Issue #531: Rollback and delayed meta save.
-</li>
-<li>Issue #515: "Unique index or primary key violation" in TestMvccMultiThreaded
-</li>
-<li>Issue #458: TIMESTAMPDIFF() test failing. Handling of timestamp literals.
-</li>
-<li>PR #546: Fixes the missing file tree.js in the web console
-</li>
-<li>Issue #543: Prepare statement with regexp will not refresh parameter after metadata change
-</li>
-<li>PR #536: Support TIMESTAMP_WITH_TIMEZONE 2014 JDBC type
-</li>
-<li>Fix bug in parsing ANALYZE TABLE xxx SAMPLE_SIZE yyy
-</li>
-<li>Add padding for CHAR(N) values in PostgreSQL mode
-</li>
-<li>Issue #89: Add DB2 timestamp format compatibility
-</li>
-</ul>
-
-<h2>Version 1.4.196 (2017-06-10)</h2>
-<ul>
-<li>Issue#479 Allow non-recursive CTEs (WITH statements), patch from stumc
-</li>
-<li>Fix startup issue when using "CHECK" as a column name.
-</li>
-<li>Issue #423: ANALYZE performed multiple times on one table during execution of the same statement.
-</li>
-<li>Issue #426: Support ANALYZE TABLE statement
-</li>
-<li>Issue #438: Fix slow logging via SLF4J (TRACE_LEVEL_FILE=4).
-</li>
-<li>Issue #472: Support CREATE SEQUENCE ... ORDER as a NOOP for Oracle compatibility
-</li>
-<li>Issue #479: Allow non-recursive Common Table Expressions (CTE)
-</li>
-<li>On Mac OS X, with IPv6 and no network connection, the Console tool was not working as expected.
-</li>
-</ul>
-
-<h2>Version 1.4.195 (2017-04-23)</h2>
-<ul>
-<li>Lazy query execution support.
-</li>
-<li>Added API for handling custom data types (System property "h2.customDataTypesHandler", API org.h2.api.CustomDataTypesHandler).
-</li>
-<li>Added support for invisible columns.
-</li>
-<li>Added an ENUM data type, with syntax similar to that of MySQL.
-</li>
-<li>MVStore: for object data types, the cache size memory estimation
- was sometimes far off in a read-only scenario.
- This could result in inefficient cache usage.
-</li>
-</ul>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/cheatSheet.html b/modules/h2/src/docsrc/html/cheatSheet.html
deleted file mode 100644
index 16237e5..0000000
--- a/modules/h2/src/docsrc/html/cheatSheet.html
+++ /dev/null
@@ -1,216 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-H2 Database Engine
-</title>
-<style type="text/css">
-td, input, select, textarea, body, td, th {
- font: 13px Arial, sans-serif;
-}
-h1, h2, h3, h4, h5 {
- font: 13px Arial, sans-serif;
- font-weight: bold;
-}
-h1 {
- background-color: #0000bb;
- padding: 2px 4px 2px 4px;
- margin-bottom: 0px;
- color: #fff;
- font-size: 19px;
- line-height: normal;
-}
-h2 {
- font-size: 16px;
-}
-a.link {
- text-decoration: underline;
- color: blue;
-}
-a.link:hover {
- text-decoration: underline;
- color: blue;
-}
-a {
- text-decoration: none;
- color: black;
-}
-a:hover {
- text-decoration: underline;
- color: blue;
-}
-td, input, select, textarea, body, code, pre {
- font: 13px Arial, sans-serif;
-}
-pre {
- background-color: #ece9d8;
- border: 1px solid #aca899;
- padding: 6px;
-
- -moz-border-radius: 4px;
- -webkit-border-radius: 4px;
- -khtml-border-radius: 4px;
- border-radius: 4px;
-
- -moz-box-shadow: 2px 2px 2px #aca899;
- -webkit-box-shadow: 2px 2px 2px #aca899;
- -khtml-box-shadow: 2px 2px 2px #aca899;
- -o-box-shadow: 2px 2px 2px #aca899;
- box-shadow: 2px 2px 2px #aca899;
-}
-code {
- background-color: #ece9d8;
- padding: 0px 4px;
-
- -moz-border-radius: 4px;
- -webkit-border-radius: 4px;
- -khtml-border-radius: 4px;
- border-radius: 4px;
-}
-table {
- background-color: #ffffff;
- border-collapse: collapse;
- border: 0px solid #aca899;
-}
-th {
- text-align: left;
- background-color: #ece9d8;
- border: 1px solid #aca899;
- padding: 2px;
-}
-td {
- background-color: #ffffff;
- text-align: left;
- vertical-align: top;
- border: 0px solid #aca899;
- padding: 2px;
-}
-ul, ol {
- list-style-position: outside;
- padding-left: 20px;
-}
-li {
- margin-top: 2px;
-}
-</style>
-</head><body>
-
-<div style="width:780px; margin:0 auto;">
-
-<h1>H2 Database Engine Cheat Sheet</h1>
-<div style="float:left; margin:5px; width:370px;">
-
-<h2>Using H2</h2>
-<ul><li><a href="http://h2database.com">H2</a> is
- <a href="https://github.com/h2database/h2database">open source</a>,
- <a href="license.html">free to use and distribute</a>.
-</li><li><a href="http://h2database.com/html/download.html">Download</a>:
- <a href="http://repo1.maven.org/maven2/com/h2database/h2/${version}/h2-${version}.jar" class="link">jar</a>,
- <a href="http://www.h2database.com/h2-setup-${versionDate}.exe" class="link">installer (Windows)</a>,
- <a href="http://www.h2database.com/h2-${versionDate}.zip" class="link">zip</a>.
-</li><li>To start the
- <a href="quickstart.html#h2_console">H2 Console tool</a>, double click the jar file, or
- run <code>java -jar h2*.jar</code>, <code>h2.bat</code>, or <code>h2.sh</code>.
-</li><li><a href="tutorial.html#creating_new_databases">A new database is automatically created</a>
- <a href="features.html#database_only_if_exists">by default</a>.
-</li><li><a href="features.html#closing_a_database">Closing the last connection closes the database</a>.
-</li></ul>
-
-<h2>Documentation</h2>
-<p>
-Reference:
-<a href="grammar.html" class="link">SQL grammar</a>,
-<a href="functions.html" class="link">functions</a>,
-<a href="datatypes.html" class="link">data types</a>,
-<a href="tutorial.html#command_line_tools" class="link">tools</a>,
-<a href="../javadoc/index.html" class="link">API</a>
-<br />
-<a href="features.html">Features</a>:
-<a href="tutorial.html#fulltext" class="link">fulltext search</a>,
-<a href="features.html#file_encryption" class="link">encryption</a>,
-<a href="features.html#read_only" class="link">read-only</a>
-<a href="features.html#database_in_zip" class="link">(zip/jar)</a>,
-<a href="tutorial.html#csv" class="link">CSV</a>,
-<a href="features.html#auto_reconnect" class="link">auto-reconnect</a>,
-<a href="features.html#triggers" class="link">triggers</a>,
-<a href="features.html#user_defined_functions" class="link">user functions</a>
-</p>
-
-<h2><a href="features.html#database_url">Database URLs</a></h2>
-<p>
-<b><a href="features.html#connection_modes">Embedded</a></b><br />
-<code>jdbc:h2:~/test</code> 'test' in the user home directory<br />
-<code>jdbc:h2:/data/test</code> 'test' in the directory /data<br />
-<code>jdbc:h2:./test</code> in the current(!) working directory<br />
-</p><p>
-<b><a href="features.html#in_memory_databases">In-Memory</a></b><br />
-<code>jdbc:h2:mem:test</code> multiple connections in one process<br />
-<code>jdbc:h2:mem:</code> unnamed private; one connection<br />
-</p><p>
-<b><a href="tutorial.html#using_server">Server Mode</a></b><br />
-<code>jdbc:h2:tcp://localhost/~/test</code> user home dir<br />
-<code>jdbc:h2:tcp://localhost//data/test</code> absolute dir<br />
-<a href="tutorial.html#using_server">Server start</a>:<code>java -cp *.jar org.h2.tools.Server</code>
-</p><p>
-<b><a href="features.html#database_url">Settings</a></b><br />
-<code>jdbc:h2:..;MODE=MySQL</code> <a href="features.html#compatibility" >compatibility (or HSQLDB,...)</a><br />
-<code>jdbc:h2:..;TRACE_LEVEL_FILE=3</code> <a href="features.html#trace_options">log to *.trace.db</a><br />
-</p>
-
-</div>
-<div style="float:right; padding:5px; width:370px;">
-
-<h2><a href="tutorial.html#connecting_using_jdbc">Using the JDBC API</a></h2>
-<pre>
-Connection conn = DriverManager.
- getConnection("jdbc:h2:~/test");
-conn.close();
-</pre>
-
-<h2><a href="tutorial.html#connection_pool">Connection Pool</a></h2>
-<pre>
-import org.h2.jdbcx.JdbcConnectionPool;
-JdbcConnectionPool cp = JdbcConnectionPool.
- create("jdbc:h2:~/test", "sa", "sa");
-Connection conn = cp.getConnection();
-conn.close(); cp.dispose();
-</pre>
-
-<h2><a href="build.html#maven2">Maven 2</a></h2>
-<pre>
-<dependency>
- <groupId>com.h2database</groupId>
- <artifactId>h2</artifactId>
- <version>${version}</version>
-</dependency>
-</pre>
-
-<h2><a href="tutorial.html#using_hibernate">Hibernate</a></h2>
-<p>
-hibernate.cfg.xml (or use the HSQLDialect):
-</p>
-<pre>
-<property name="dialect">
- org.hibernate.dialect.H2Dialect
-</property>
-</pre>
-
-<h2><a href="tutorial.html#using_toplink">TopLink and Glassfish</a></h2>
-<p>
-Datasource class: <code>org.h2.jdbcx.JdbcDataSource</code><br />
-<code>oracle.toplink.essentials.platform.</code><br />
-<code>database.H2Platform</code>
-</p>
-
-</div>
-
-</div>
-
-</body></html>
\ No newline at end of file
diff --git a/modules/h2/src/docsrc/html/commands.html b/modules/h2/src/docsrc/html/commands.html
deleted file mode 100644
index 3e92a63..0000000
--- a/modules/h2/src/docsrc/html/commands.html
+++ /dev/null
@@ -1,179 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Commands
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Commands</h1>
-<h2 id="commands_index">Index</h2>
-<h3>Commands (Data Manipulation)</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="commandsDML">
- <a href="#${item.link}">${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="commandsDML-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsDML-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsDML-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Commands (Data Definition)</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="commandsDDL">
- <a href="#${item.link}">${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="commandsDDL-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsDDL-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsDDL-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Commands (Other)</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="commandsOther">
- <a href="#${item.link}">${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="commandsOther-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsOther-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="commandsOther-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<!-- railroad-start -->
-<h2>Details</h2>
-<p>Click on the header to switch between railroad diagram and BNF.</p>
-<!-- railroad-end -->
-
-<h2>Commands (Data Manipulation)</h2>
-<c:forEach var="item" items="commandsDML">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">
-${item.example}</p>
-</c:forEach>
-
-<h2>Commands (Data Definition)</h2>
-<c:forEach var="item" items="commandsDDL">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">
-${item.example}</p>
-</c:forEach>
-
-<h2>Commands (Other)</h2>
-<c:forEach var="item" items="commandsOther">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">
-${item.example}</p>
-</c:forEach>
-
-<!--[if lte IE 7]><script language="javascript">switchBnf(null);</script><![endif]-->
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/datatypes.html b/modules/h2/src/docsrc/html/datatypes.html
deleted file mode 100644
index 41eddf8..0000000
--- a/modules/h2/src/docsrc/html/datatypes.html
+++ /dev/null
@@ -1,99 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Data Types
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Data Types</h1>
-<h2 id="datatypes_index">Index</h2>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="dataTypes">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="dataTypes-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="dataTypes-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="dataTypes-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<!-- railroad-start -->
-<h2>Details</h2>
-<p>Click on the header to switch between railroad diagram and BNF.</p>
-<!-- railroad-end -->
-
-<c:forEach var="item" items="dataTypes">
-<h2 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h2>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>Interval Data Types</h2>
-
-<c:forEach var="item" items="intervalDataTypes">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<!--[if lte IE 7]><script language="javascript">switchBnf(null);</script><![endif]-->
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/download.html b/modules/h2/src/docsrc/html/download.html
deleted file mode 100644
index f68a60f..0000000
--- a/modules/h2/src/docsrc/html/download.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Downloads
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Downloads</h1>
-
-<h3>Version ${version} (${versionDate})</h3>
-<p>
-<a href="http://www.h2database.com/h2-setup-${versionDate}.exe">Windows Installer</a>
-<!-- sha1Exe --><br />
-<a href="http://www.h2database.com/h2-${versionDate}.zip">Platform-Independent Zip</a>
-<!-- sha1Zip --><br />
-</p>
-
-<h3>Version ${stableVersion} (${stableVersionDate}), Last Stable</h3>
-<p>
-<a href="http://www.h2database.com/h2-setup-${stableVersionDate}.exe">Windows Installer</a><br />
-<a href="http://www.h2database.com/h2-${stableVersionDate}.zip">Platform-Independent Zip</a><br />
-</p>
-
-<h3>Old Versions</h3>
-<p>
-<a href="http://code.google.com/p/h2database/downloads/list">Platform-Independent Zip</a><br />
-</p>
-
-<h3>Jar File</h3>
-<p>
-<a href="http://repo2.maven.org/maven2/com/h2database/h2/${version}/h2-${version}.jar">Maven.org</a><br />
-<a href="http://hsql.sourceforge.net/m2-repo/com/h2database/h2/${version}/h2-${version}.jar">Sourceforge.net</a><br />
-</p>
-
-<h3>Maven (Binary, Javadoc, and Source)</h3>
-<p>
-<a href="http://repo2.maven.org/maven2/com/h2database/h2/${version}/h2-${version}.jar">Binary</a><br />
-<a href="http://repo2.maven.org/maven2/com/h2database/h2/${version}/h2-${version}-javadoc.jar">Javadoc</a><br />
-<a href="http://repo2.maven.org/maven2/com/h2database/h2/${version}/h2-${version}-sources.jar">Sources</a><br />
-</p>
-
-<h3>Database Upgrade Helper File</h3>
-<p>
-<a href="http://h2database.com/h2mig_pagestore_addon.jar">Upgrade database from 1.1 to the current version</a>
-</p>
-
-<h3>Git Source Repository</h3>
-<p>
-<a href="https://github.com/h2database/h2database">Github</a>
-</p>
-
-<p>
-For details about changes, see the <a href="changelog.html">Change Log</a>.
-</p>
-
-<h3>News and Project Information</h3>
-<p>
-<a href="http://www.h2database.com/html/newsfeed-atom.xml">Atom Feed</a><br />
-<a href="http://www.h2database.com/html/newsfeed-rss.xml">RSS Feed</a><br />
-<a href="http://www.h2database.com/html/doap-h2.rdf">DOAP File</a> (<a href="http://en.wikipedia.org/wiki/DOAP">what is this</a>)
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/faq.html b/modules/h2/src/docsrc/html/faq.html
deleted file mode 100644
index fcda24a..0000000
--- a/modules/h2/src/docsrc/html/faq.html
+++ /dev/null
@@ -1,288 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Frequently Asked Questions
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1 id="faq_index">Frequently Asked Questions</h1>
-
-<a href="#support">
- I Have a Problem or Feature Request</a><br />
-<a href="#known_bugs">
- Are there Known Bugs? When is the Next Release?</a><br />
-<a href="#open_source">
- Is this Database Engine Open Source?</a><br />
-<a href="#commercial_support">
- Is Commercial Support Available?</a><br />
-<a href="#create_database">
- How to Create a New Database?</a><br />
-<a href="#connect">
- How to Connect to a Database?</a><br />
-<a href="#database_files">
- Where are the Database Files Stored?</a><br />
-<a href="#size_limit">
- What is the Size Limit (Maximum Size) of a Database?</a><br />
-<a href="#reliable">
- Is it Reliable?</a><br />
-<a href="#slow_open">
- Why is Opening my Database Slow?</a><br />
-<a href="#query_slow">
- My Query is Slow</a><br />
-<a href="#database_slow">
- H2 is Very Slow</a><br />
-<a href="#column_names_incorrect">
- Column Names are Incorrect?</a><br />
-<a href="#float_is_double">
- Float is Double?</a><br />
-<a href="#how_to_translate">
- How to Translate this Project?</a><br />
-<a href="#how_to_contribute">
- How to Contribute to this Project?</a><br />
-
-<h3 id="support">I Have a Problem or Feature Request</h3>
-<p>
-Please read the <a href="build.html#support">support checklist</a>.
-</p>
-
-<h3 id="known_bugs">Are there Known Bugs? When is the Next Release?</h3>
-<p>
-Usually, bugs get fixes as they are found. There is a release every few weeks.
-Here is the list of known and confirmed issues:
-</p>
-<ul><li>When opening a database file in a timezone that has different
- daylight saving rules: the time part of dates where the daylight saving doesn't match
- will differ. This is not a problem within regions that use the same rules (such as, within
- USA, or within Europe), even if the timezone itself is different. As a workaround, export the
- database to a SQL script using the old timezone, and create a new database in the new
- timezone.
-</li><li>Tomcat and Glassfish 3 set most static fields (final or non-final) to <code>null</code> when
- unloading a web application. This can cause a <code>NullPointerException</code> in H2 versions
- 1.1.107 and older, and may still not work in newer versions. Please report it if you
- run into this issue. In Tomcat >= 6.0 this behavior can be disabled by setting the
- system property <code>org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false</code>,
- however Tomcat may then run out of memory. A known workaround is to
- put the <code>h2*.jar</code> file in a shared <code>lib</code> directory
- (<code>common/lib</code>).
-</li><li>Some problems have been found with right outer join. Internally, it is converted
- to left outer join, which does not always produce the same results as other databases
- when used in combination with other joins. This problem is fixed in H2 version 1.3.
-</li></ul>
-<p>
-For a complete list, see <a href="https://github.com/h2database/h2database/issues">Open Issues</a>.
-</p>
-
-<h3 id="open_source">Is this Database Engine Open Source?</h3>
-<p>
-Yes. It is free to use and distribute, and the source code is included.
-See also under license.
-</p>
-
-<h3 id="commercial_support">Is Commercial Support Available?</h3>
-<p>
-No, currently commercial support is not available.
-</p>
-
-<h3 id="create_database">How to Create a New Database?</h3>
-<p>
-By default, a new database is automatically created if it does not yet exist when
-<a href="features.html#database_url">embedded</a> URL is used.
-See <a href="tutorial.html#creating_new_databases">Creating New Databases</a>.
-</p>
-
-<h3 id="connect">How to Connect to a Database?</h3>
-<p>
-The database driver is <code>org.h2.Driver</code>,
-and the database URL starts with <code>jdbc:h2:</code>.
-To connect to a database using JDBC, use the following code:
-</p>
-<pre>
-Connection conn = DriverManager.getConnection("jdbc:h2:~/test", "sa", "");
-</pre>
-
-<h3 id="database_files">Where are the Database Files Stored?</h3>
-<p>
-When using database URLs like <code>jdbc:h2:~/test</code>,
-the database is stored in the user directory.
-For Windows, this is usually
-<code>C:\Documents and Settings\<userName></code> or
-<code>C:\Users\<userName></code>.
-If the base directory is not set (as in <code>jdbc:h2:./test</code>),
-the database files are stored in the directory where the application is started
-(the current working directory).
-When using the H2 Console application from the start menu,
-this is <code><Installation Directory>/bin</code>.
-The base directory can be set in the database URL.
-A fixed or relative path can be used. When using the URL
-<code>jdbc:h2:file:./data/sample</code>, the database is stored in the directory
-<code>data</code> (relative to the current working directory).
-The directory is created automatically if it does not yet exist.
-It is also possible to use the fully qualified directory name (and for Windows, drive name).
-Example: <code>jdbc:h2:file:C:/data/test</code>
-</p>
-
-<h3 id="size_limit">What is the Size Limit (Maximum Size) of a Database?</h3>
-<p>
-See <a href="advanced.html#limits_limitations">Limits and Limitations</a>.
-</p>
-
-<h3 id="reliable">Is it Reliable?</h3>
-<p>
-That is not easy to say. It is still a quite new product. A lot of tests have been written,
-and the code coverage of these tests is higher than 80% for each package.
-Randomized stress tests are run regularly. But there are probably still
-bugs that have not yet been found (as with most software). Some features are known
-to be dangerous, they are only supported for situations where performance is more important
-than reliability. Those dangerous features are:
-</p>
-<ul><li>Disabling the transaction log or FileDescriptor.sync() using LOG=0 or LOG=1.
-</li><li>Using the transaction isolation level <code>READ_UNCOMMITTED</code>
- (<code>LOCK_MODE 0</code>) while at the same time using multiple
- connections.
-</li><li>Disabling database file protection using (setting <code>FILE_LOCK</code> to
- <code>NO</code> in the database URL).
-</li><li>Disabling referential integrity using <code>SET REFERENTIAL_INTEGRITY FALSE</code>.
-</li></ul>
-<p>
-In addition to that, running out of memory should be avoided.
-In older versions, OutOfMemory errors while using the database could corrupt a databases.
-</p>
-<p>
-This database is well tested using automated test cases. The tests run every night
-and run for more than one hour. But not all areas of this database are equally well tested.
-When using one of the following features for production, please ensure your use case
-is well tested (if possible with automated test cases). The areas that are not well tested are:
-</p>
-<ul>
-<li>Platforms other than Windows, Linux, Mac OS X, or runtime environments other than Oracle / OpenJDK 7, 8, 9.
-</li><li>The features <code>AUTO_SERVER</code> and <code>AUTO_RECONNECT</code>.
-</li><li>Cluster mode, 2-phase commit, savepoints.
-</li><li>Fulltext search.
-</li><li>Operations on LOBs over 2 GB.
-</li><li>The optimizer may not always select the best plan.
-</li><li>Using the ICU4J collator.
-</li></ul>
-<p>
-Areas considered experimental are:
-</p>
-<ul>
-<li>The PostgreSQL server
-</li><li>Clustering (there are cases were transaction isolation can be broken
- due to timing issues, for example one session overtaking another session).
-</li><li>Multi-threading within the old PageStore engine using <code>SET MULTI_THREADED=1</code>.
- Default MVStore engine is multi-threaded by default.
-</li><li>Compatibility modes for other databases (only some features are implemented).
-</li><li>The soft reference cache (<code>CACHE_TYPE=SOFT_LRU</code>). It might not improve performance,
- and out of memory issues have been reported.
-</li></ul>
-<p>
-Some users have reported that after a power failure, the database cannot be opened sometimes.
-In this case, use a backup of the database or the Recover tool. Please report such problems.
-The plan is that the database automatically recovers in all situations.
-</p>
-
-<h3 id="slow_open">Why is Opening my Database Slow?</h3>
-<p>
-To find out what the problem is, use the H2 Console and click on "Test Connection"
-instead of "Login". After the "Login Successful" appears, click on it (it's a link).
-This will list the top stack traces. Then either analyze this yourself, or
-post those stack traces in the Google Group.
-</p>
-<p>
-Other possible reasons are: the database is very big (many GB), or contains linked tables
-that are slow to open.
-</p>
-
-<h3 id="query_slow">My Query is Slow</h3>
-<p>
-Slow <code>SELECT</code> (or <code>DELETE, UPDATE, MERGE</code>)
-statement can have multiple reasons. Follow this checklist:
-</p>
-<ul>
-<li>Run <code>ANALYZE</code> (see documentation for details).
-</li><li>Run the query with <code>EXPLAIN</code> and check if indexes are used
- (see documentation for details).
-</li><li>If required, create additional indexes and try again using
- <code>ANALYZE</code> and <code>EXPLAIN</code>.
-</li><li>If it doesn't help please report the problem.
-</li>
-</ul>
-
-
-<h3 id="database_slow">H2 is Very Slow</h3>
-<p>
-By default, H2 closes the database when the last connection is closed.
-If your application closes the only connection after each operation,
-the database is opened and closed a lot, which is quite slow.
-There are multiple ways to solve this problem, see
-<a href="performance.html#database_performance_tuning">Database Performance Tuning</a>.
-</p>
-
-<h3 id="column_names_incorrect">Column Names are Incorrect?</h3>
-<p>
-For the query <code>SELECT ID AS X FROM TEST</code> the method
-<code>ResultSetMetaData.getColumnName()</code> returns <code>ID</code>, I expect it to
-return <code>X</code>. What's wrong?
-</p>
-<p>
-This is not a bug. According the JDBC specification, the method
-<code>ResultSetMetaData.getColumnName()</code> should return the name of the column
-and not the alias name. If you need the alias name, use
-<a href="https://docs.oracle.com/javase/7/docs/api/java/sql/ResultSetMetaData.html#getColumnLabel(int)"><code>ResultSetMetaData.getColumnLabel()</code></a>.
-Some other database don't work like this yet (they don't follow the JDBC specification).
-If you need compatibility with those databases, use the <a href="features.html#compatibility">Compatibility Mode</a>,
-or append <a href="http://www.h2database.com/javadoc/org/h2/engine/DbSettings.html#ALIAS_COLUMN_NAME"><code>;ALIAS_COLUMN_NAME=TRUE</code></a> to the database URL.
-</p>
-<p>
-This also applies to DatabaseMetaData calls that return a result set.
-The columns in the JDBC API are column labels, not column names.
-</p>
-
-<h3 id="float_is_double">Float is Double?</h3>
-<p>
-For a table defined as <code>CREATE TABLE TEST(X FLOAT)</code> the method
-<code>ResultSet.getObject()</code> returns a <code>java.lang.Double</code>, I expect it to
-return a <code>java.lang.Float</code>. What's wrong?
-</p>
-<p>
-This is not a bug. According the JDBC specification, the JDBC data type <code>FLOAT</code>
-is equivalent to <code>DOUBLE</code>, and both are mapped to <code>java.lang.Double</code>.
-See also
-<a href="https://docs.oracle.com/javase/1.5.0/docs/guide/jdbc/getstart/mapping.html#1055162">
-Mapping SQL and Java Types - 8.3.10 FLOAT</a>.</p>
-<p>Use REAL or FLOAT(24) data type for <code>java.lang.Float</code> values.</p>
-
-<h3 id="how_to_translate">How to Translate this Project?</h3>
-<p>
-For more information, see
-<a href="build.html#translating">Build/Translating</a>.
-</p>
-
-<h3 id="how_to_contribute">How to Contribute to this Project?</h3>
-<p>
-There are various way to help develop an open source project like H2. The first step could be to
-<a href="build.html#translating">translate</a> the error messages and the GUI to your native language.
-Then, you could
-<a href="build.html#providing_patches">provide patches</a>.
-Please start with small patches. That could be adding a test case to improve the
-<a href="build.html#automated">code coverage</a> (the target code coverage for this project is 90%, higher is better).
-You will have to <a href="build.html">develop, build and run the tests</a>.
-Once you are familiar with the code, you could implement missing features from the
-<a href="http://www.h2database.com/html/roadmap.html">feature request list</a>.
-I suggest to start with very small features that are easy to implement.
-Keep in mind to provide test cases as well.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/features.html b/modules/h2/src/docsrc/html/features.html
deleted file mode 100644
index 4c802f1..0000000
--- a/modules/h2/src/docsrc/html/features.html
+++ /dev/null
@@ -1,1719 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Features
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Features</h1>
-
-<a href="#feature_list">
- Feature List</a><br />
-<a href="#products_work_with">
- H2 in Use</a><br />
-<a href="#connection_modes">
- Connection Modes</a><br />
-<a href="#database_url">
- Database URL Overview</a><br />
-<a href="#embedded_databases">
- Connecting to an Embedded (Local) Database</a><br />
-<a href="#in_memory_databases">
- In-Memory Databases</a><br />
-<a href="#file_encryption">
- Database Files Encryption</a><br />
-<a href="#database_file_locking">
- Database File Locking</a><br />
-<a href="#database_only_if_exists">
- Opening a Database Only if it Already Exists</a><br />
-<a href="#closing_a_database">
- Closing a Database</a><br />
-<a href="#ignore_unknown_settings">
- Ignore Unknown Settings</a><br />
-<a href="#other_settings">
- Changing Other Settings when Opening a Connection</a><br />
-<a href="#custom_access_mode">
- Custom File Access Mode</a><br />
-<a href="#multiple_connections">
- Multiple Connections</a><br />
-<a href="#database_file_layout">
- Database File Layout</a><br />
-<a href="#logging_recovery">
- Logging and Recovery</a><br />
-<a href="#compatibility">
- Compatibility</a><br />
-<a href="#auto_reconnect">
- Auto-Reconnect</a><br />
-<a href="#auto_mixed_mode">
- Automatic Mixed Mode</a><br />
-<a href="#page_size">
- Page Size</a><br />
-<a href="#trace_options">
- Using the Trace Options</a><br />
-<a href="#other_logging">
- Using Other Logging APIs</a><br />
-<a href="#read_only">
- Read Only Databases</a><br />
-<a href="#database_in_zip">
- Read Only Databases in Zip or Jar File</a><br />
-<a href="#computed_columns">
- Computed Columns / Function Based Index</a><br />
-<a href="#multi_dimensional">
- Multi-Dimensional Indexes</a><br />
-<a href="#user_defined_functions">
- User-Defined Functions and Stored Procedures</a><br />
-<a href="#pluggable_tables">
- Pluggable or User-Defined Tables</a><br />
-<a href="#triggers">
- Triggers</a><br />
-<a href="#compacting">
- Compacting a Database</a><br />
-<a href="#cache_settings">
- Cache Settings</a><br />
-<a href="#external_authentication">
- External Authentication (Experimental)</a><br />
-
-<h2 id="feature_list">Feature List</h2>
-<h3>Main Features</h3>
-<ul>
-<li>Very fast database engine
-</li><li>Open source
-</li><li>Written in Java
-</li><li>Supports standard SQL, JDBC API
-</li><li>Embedded and Server mode, Clustering support
-</li><li>Strong security features
-</li><li>The PostgreSQL ODBC driver can be used
-</li><li>Multi version concurrency
-</li></ul>
-
-<h3>Additional Features</h3>
-<ul>
-<li>Disk based or in-memory databases and tables, read-only database support, temporary tables
-</li><li>Transaction support (read committed), 2-phase-commit
-</li><li>Multiple connections, table level locking
-</li><li>Cost based optimizer, using a genetic algorithm for complex queries, zero-administration
-</li><li>Scrollable and updatable result set support, large result set, external result sorting,
- functions can return a result set
-</li><li>Encrypted database (AES), SHA-256 password encryption, encryption functions, SSL
-</li></ul>
-
-<h3>SQL Support</h3>
-<ul>
-<li>Support for multiple schemas, information schema
-</li><li>Referential integrity / foreign key constraints with cascade, check constraints
-</li><li>Inner and outer joins, subqueries, read only views and inline views
-</li><li>Triggers and Java functions / stored procedures
-</li><li>Many built-in functions, including XML and lossless data compression
-</li><li>Wide range of data types including large objects (BLOB/CLOB) and arrays
-</li><li>Sequence and autoincrement columns, computed columns (can be used for function based indexes)
-</li><li>ORDER BY, GROUP BY, HAVING, UNION, OFFSET / FETCH (including PERCENT and WITH TIES), LIMIT, TOP,
- DISTINCT / DISTINCT ON (...)
-</li><li>Window functions
-</li><li>Collation support, including support for the ICU4J library
-</li><li>Support for users and roles
-</li><li>Compatibility modes for IBM DB2, Apache Derby, HSQLDB,
- MS SQL Server, MySQL, Oracle, and PostgreSQL.
-</li></ul>
-
-<h3>Security Features</h3>
-<ul>
-<li>Includes a solution for the SQL injection problem
-</li><li>User password authentication uses SHA-256 and salt
-</li><li>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)
-</li><li>All database files (including script files that can be used to backup data) can be
-encrypted using the AES-128 encryption algorithm
-</li><li>The remote JDBC driver supports TCP/IP connections over TLS
-</li><li>The built-in web server supports connections over TLS
-</li><li>Passwords can be sent to the database using char arrays instead of Strings
-</li></ul>
-
-<h3>Other Features and Tools</h3>
-<ul>
-<li>Small footprint (around 2 MB), low memory requirements
-</li><li>Multiple index types (b-tree, tree, hash)
-</li><li>Support for multi-dimensional indexes
-</li><li>CSV (comma separated values) file support
-</li><li>Support for linked tables, and a built-in virtual 'range' table
-</li><li>Supports the <code>EXPLAIN PLAN</code> statement; sophisticated trace options
-</li><li>Database closing can be delayed or disabled to improve the performance
-</li><li>Web-based Console application (translated to many languages) with autocomplete
-</li><li>The database can generate SQL script files
-</li><li>Contains a recovery tool that can dump the contents of the database
-</li><li>Support for variables (for example to calculate running totals)
-</li><li>Automatic re-compilation of prepared statements
-</li><li>Uses a small number of database files
-</li><li>Uses a checksum for each record and log entry for data integrity
-</li><li>Well tested (high code coverage, randomized stress tests)
-</li></ul>
-
-<h2 id="products_work_with">H2 in Use</h2>
-<p>
-For a list of applications that work with or use H2, see:
-<a href="http://www.h2database.com/html/links.html">Links</a>.
-</p>
-
-<h2 id="connection_modes">Connection Modes</h2>
-<p>
-The following connection modes are supported:
-</p>
-<ul>
-<li>Embedded mode (local connections using JDBC)
-</li><li>Server mode (remote connections using JDBC or ODBC over TCP/IP)
-</li><li>Mixed mode (local and remote connections at the same time)
-</li></ul>
-
-<h3>Embedded Mode</h3>
-<p>
-In embedded mode, an application opens a database from within the same JVM using JDBC.
-This is the fastest and easiest connection mode.
-The disadvantage is that a database may only be open in one virtual machine (and class loader) at any time.
-As in all modes, both persistent and in-memory databases are supported.
-There is no limit on the number of database open concurrently,
-or on the number of open connections.
-</p>
-<img src="images/connection-mode-embedded-2.png"
- width="208" height="259"
- alt="The database is embedded in the application" />
-
-<h3>Server Mode</h3>
-<p>
-When using the server mode (sometimes called remote mode or client/server mode),
-an application opens a database remotely using the JDBC or ODBC API.
-A server needs to be started within the same or another virtual machine, or on another computer.
-Many applications can connect to the same database at the same time, by connecting to this server.
-Internally, the server process opens the database(s) in embedded mode.
-</p>
-<p>
-The server mode is slower than the embedded mode, because all data is transferred over TCP/IP.
-As in all modes, both persistent and in-memory databases are supported.
-There is no limit on the number of database open concurrently per server,
-or on the number of open connections.
-</p>
-<img src="images/connection-mode-remote-2.png"
- width="376" height="218"
- alt="The database is running in a server; the application connects to the server" />
-
-<h3>Mixed Mode</h3>
-<p>
-The mixed mode is a combination of the embedded and the server mode.
-The first application that connects to a database does that in embedded mode, but also starts
-a server so that other applications (running in different processes or virtual machines) can
-concurrently access the same data. The local connections are as fast as if
-the database is used in just the embedded mode, while the remote
-connections are a bit slower.
-</p><p>
-The server can be started and stopped from within the application (using the server API),
-or automatically (automatic mixed mode). When using the <a href="#auto_mixed_mode">automatic mixed mode</a>,
-all clients that want to connect to the database (no matter if
-it's an local or remote connection) can do so using the exact same database URL.
-</p>
-<img src="images/connection-mode-mixed-2.png"
- width="403" height="240"
- alt="Database, server, and application run in one JVM; an application connects" />
-
-<h2 id="database_url">Database URL Overview</h2>
-<p>
-This database supports multiple connection modes and connection settings.
-This is achieved using different database URLs. Settings in the URLs are not case sensitive.
-</p>
-<table class="main">
-<tr><th>Topic</th><th>URL Format and Examples</th></tr>
-<tr>
- <td><a href="#embedded_databases">Embedded (local) connection</a></td>
- <td class="notranslate">
- jdbc:h2:[file:][<path>]<databaseName><br />
- jdbc:h2:~/test<br />
- jdbc:h2:file:/data/sample<br />
- jdbc:h2:file:C:/data/sample (Windows only)<br />
- </td>
-</tr>
-<tr>
- <td><a href="#in_memory_databases">In-memory (private)</a></td>
- <td class="notranslate">jdbc:h2:mem:</td>
-</tr>
-<tr>
- <td><a href="#in_memory_databases">In-memory (named)</a></td>
- <td class="notranslate">
- jdbc:h2:mem:<databaseName><br />
- jdbc:h2:mem:test_mem
- </td>
-</tr>
-<tr>
- <td><a href="tutorial.html#using_server">Server mode (remote connections)<br /> using TCP/IP</a></td>
- <td class="notranslate">
- jdbc:h2:tcp://<server>[:<port>]/[<path>]<databaseName><br />
- jdbc:h2:tcp://localhost/~/test<br />
- jdbc:h2:tcp://dbserv:8084/~/sample<br />
- jdbc:h2:tcp://localhost/mem:test<br />
- </td>
-</tr>
-<tr>
- <td><a href="advanced.html#tls_connections">Server mode (remote connections)<br /> using TLS</a></td>
- <td class="notranslate">
- jdbc:h2:ssl://<server>[:<port>]/[<path>]<databaseName><br />
- jdbc:h2:ssl://localhost:8085/~/sample;
- </td>
-</tr>
-<tr>
- <td><a href="#file_encryption">Using encrypted files</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;CIPHER=AES<br />
- jdbc:h2:ssl://localhost/~/test;CIPHER=AES<br />
- jdbc:h2:file:~/secure;CIPHER=AES<br />
- </td>
-</tr>
-<tr>
- <td><a href="#database_file_locking">File locking methods</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;FILE_LOCK={FILE|SOCKET|NO}<br />
- jdbc:h2:file:~/private;CIPHER=AES;FILE_LOCK=SOCKET<br />
- </td>
-</tr>
-<tr>
- <td><a href="#database_only_if_exists">Only open if it already exists</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;IFEXISTS=TRUE<br />
- jdbc:h2:file:~/sample;IFEXISTS=TRUE<br />
- </td>
-</tr>
-<tr>
- <td><a href="#do_not_close_on_exit">Don't close the database when the VM exits</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;DB_CLOSE_ON_EXIT=FALSE
- </td>
-</tr>
-<tr>
- <td><a href="#execute_sql_on_connection">Execute SQL on connection</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;INIT=RUNSCRIPT FROM '~/create.sql'<br />
- jdbc:h2:file:~/sample;INIT=RUNSCRIPT FROM '~/create.sql'\;RUNSCRIPT FROM '~/populate.sql'<br />
- </td>
-</tr>
-<tr>
- <td><a href="advanced.html#passwords">User name and/or password</a></td>
- <td class="notranslate">
- jdbc:h2:<url>[;USER=<username>][;PASSWORD=<value>]<br />
- jdbc:h2:file:~/sample;USER=sa;PASSWORD=123<br />
- </td>
-</tr>
-<tr>
- <td><a href="#trace_options">Debug trace settings</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;TRACE_LEVEL_FILE=<level 0..3><br />
- jdbc:h2:file:~/sample;TRACE_LEVEL_FILE=3<br />
- </td>
-</tr>
-<tr>
- <td><a href="#ignore_unknown_settings">Ignore unknown settings</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;IGNORE_UNKNOWN_SETTINGS=TRUE<br />
- </td>
-</tr>
-<tr>
- <td><a href="#custom_access_mode">Custom file access mode</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;ACCESS_MODE_DATA=rws<br />
- </td>
-</tr>
-<tr>
- <td><a href="#database_in_zip">Database in a zip file</a></td>
- <td class="notranslate">
- jdbc:h2:zip:<zipFileName>!/<databaseName><br />
- jdbc:h2:zip:~/db.zip!/test
- </td>
-</tr>
-<tr>
- <td><a href="#compatibility">Compatibility mode</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;MODE=<databaseType><br />
- jdbc:h2:~/test;MODE=MYSQL;DATABASE_TO_LOWER=TRUE
- </td>
-</tr>
-<tr>
- <td><a href="#auto_reconnect">Auto-reconnect</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;AUTO_RECONNECT=TRUE<br />
- jdbc:h2:tcp://localhost/~/test;AUTO_RECONNECT=TRUE
- </td>
-</tr>
-<tr>
- <td><a href="#auto_mixed_mode">Automatic mixed mode</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;AUTO_SERVER=TRUE<br />
- jdbc:h2:~/test;AUTO_SERVER=TRUE
- </td>
-</tr>
-<tr>
- <td><a href="#page_size">Page size</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;PAGE_SIZE=512<br />
- </td>
-</tr>
-<tr>
- <td><a href="#other_settings">Changing other settings</a></td>
- <td class="notranslate">
- jdbc:h2:<url>;<setting>=<value>[;<setting>=<value>...]<br />
- jdbc:h2:file:~/sample;TRACE_LEVEL_SYSTEM_OUT=3<br />
- </td>
-</tr>
-</table>
-
-<h2 id="embedded_databases">Connecting to an Embedded (Local) Database</h2>
-<p>
-The database URL for connecting to a local database is
-<code>jdbc:h2:[file:][<path>]<databaseName></code>.
-The prefix <code>file:</code> is optional. If no or only a relative path is used, then the current working
-directory is used as a starting point. The case sensitivity of the path and database name depend on the
-operating system, however it is recommended to use lowercase letters only.
-The database name must be at least three characters long
-(a limitation of <code>File.createTempFile</code>).
-The database name must not contain a semicolon.
-To point to the user home directory, use <code>~/</code>, as in: <code>jdbc:h2:~/test</code>.
-</p>
-
-<h2 id="in_memory_databases">In-Memory Databases</h2>
-<p>
-For certain use cases (for example: rapid prototyping, testing, high performance
-operations, read-only databases), it may not be required to persist data, or persist changes to the data.
-This database supports the in-memory mode, where the data is not persisted.
-</p><p>
-In some cases, only one connection to a in-memory database is required.
-This means the database to be opened is private. In this case, the database URL is
-<code>jdbc:h2:mem:</code> Opening two connections within the same virtual machine
-means opening two different (private) databases.
-</p><p>
-Sometimes multiple connections to the same in-memory database are required.
-In this case, the database URL must include a name. Example: <code>jdbc:h2:mem:db1</code>.
-Accessing the same database using this URL only works within the same virtual machine and
-class loader environment.
-</p><p>
-To access an in-memory database from another process or from another computer,
-you need to start a TCP server in the same process as the in-memory database was created.
-The other processes then need to access the database over TCP/IP or TLS,
-using a database URL such as: <code>jdbc:h2:tcp://localhost/mem:db1</code>.
-</p><p>
-By default, closing the last connection to a database closes the database.
-For an in-memory database, this means the content is lost.
-To keep the database open, add <code>;DB_CLOSE_DELAY=-1</code> to the database URL.
-To keep the content of an in-memory database as long as the virtual machine is alive, use
-<code>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</code>.
-</p>
-
-<h2 id="file_encryption">Database Files Encryption</h2>
-<p>
-The database files can be encrypted.
-Three encryption algorithms are supported:
-</p>
-<ul>
-<li>"AES" - also known as Rijndael, only AES-128 is implemented.</li>
-<li>"XTEA" - the 32 round version.</li>
-<li>"FOG" - pseudo-encryption only useful for hiding data from a text editor.</li>
-</ul>
-<p>
-To use file encryption, you need to specify the encryption algorithm (the 'cipher')
-and the file password (in addition to the user password) when connecting to the database.
-</p>
-
-<h3>Creating a New Database with File Encryption</h3>
-<p>
-By default, a new database is automatically created if it does not exist yet
-when the <a href="#database_url">embedded</a> url is used.
-To create an encrypted database, connect to it as it would already exist locally using the embedded URL.
-</p>
-
-<h3>Connecting to an Encrypted Database</h3>
-<p>
-The encryption algorithm is set in the database URL, and the file password is specified in the password field,
-before the user password. A single space separates the file password
-and the user password; the file password itself may not contain spaces. File passwords
-and user passwords are case sensitive. Here is an example to connect to a
-password-encrypted database:
-</p>
-<pre>
-String url = "jdbc:h2:~/test;CIPHER=AES";
-String user = "sa";
-String pwds = "filepwd userpwd";
-conn = DriverManager.
- getConnection(url, user, pwds);
-</pre>
-
-<h3>Encrypting or Decrypting a Database</h3>
-<p>
-To encrypt an existing database, use the <code>ChangeFileEncryption</code> tool.
-This tool can also decrypt an encrypted database, or change the file encryption key.
-The tool is available from within the H2 Console in the tools section, or you can run it from the command line.
-The following command line will encrypt the database <code>test</code> in the user home directory
-with the file password <code>filepwd</code> and the encryption algorithm AES:
-</p>
-<pre>
-java -cp h2*.jar org.h2.tools.ChangeFileEncryption -dir ~ -db test -cipher AES -encrypt filepwd
-</pre>
-
-<h2 id="database_file_locking">Database File Locking</h2>
-<p>
-Whenever a database is opened, a lock file is created to signal other processes
-that the database is in use. If database is closed, or if the process that opened
-the database terminates, this lock file is deleted.
-</p><p>
-The following file locking methods are implemented:
-</p>
-<ul>
-<li>The default method is <code>FILE</code> and uses a watchdog thread to
-protect the database file. The watchdog reads the lock file each second.
-</li><li>The second method is <code>SOCKET</code> and opens a server socket.
-The socket method does not require reading the lock file every second.
-The socket method should only be used if the database files
-are only accessed by one (and always the same) computer.
-</li><li>The third method is <code>FS</code>.
-This will use native file locking using <code>FileChannel.lock</code>.
-</li><li>It is also possible to open the database without file locking;
-in this case it is up to the application to protect the database files.
-Failing to do so will result in a corrupted database.
-Using the method <code>NO</code> forces the database to not create a lock file at all.
-Please note that this is unsafe as another process is able to open the same database,
-possibly leading to data corruption.</li></ul>
-<p>
-To open the database with a different file locking method, use the parameter
-<code>FILE_LOCK</code>.
-The following code opens the database with the 'socket' locking method:
-</p>
-<pre>
-String url = "jdbc:h2:~/test;FILE_LOCK=SOCKET";
-</pre>
-<p>
-For more information about the algorithms, see
-<a href="advanced.html#file_locking_protocols">Advanced / File Locking Protocols</a>.
-</p>
-
-<h2 id="database_only_if_exists">Opening a Database Only if it Already Exists</h2>
-<p>
-By default, when an application calls <code>DriverManager.getConnection(url, ...)</code>
-with <a href="features.html#database_url">embedded</a> URL and the database specified in the URL does not yet exist,
-a new (empty) database is created.
-In some situations, it is better to restrict creating new databases, and only allow to open
-existing databases. To do this, add <code>;IFEXISTS=TRUE</code>
-to the database URL. In this case, if the database does not already exist, an exception is thrown when
-trying to connect. The connection only succeeds when the database already exists.
-The complete URL may look like this:
-</p>
-<pre>
-String url = "jdbc:h2:/data/sample;IFEXISTS=TRUE";
-</pre>
-
-<h2 id="closing_a_database">Closing a Database</h2>
-
-<h3>Delayed Database Closing</h3>
-<p>
-Usually, a database is closed when the last connection to it is closed. In some situations
-this slows down the application, for example when it is not possible to keep at least one connection open.
-The automatic closing of a database can be delayed or disabled with the SQL statement
-<code>SET DB_CLOSE_DELAY <seconds></code>.
-The parameter <seconds> specifies the number of seconds to keep
-a database open after the last connection to it was closed. The following statement
-will keep a database open for 10 seconds after the last connection was closed:
-</p>
-<pre>
-SET DB_CLOSE_DELAY 10
-</pre>
-<p>
-The value -1 means the database is not closed automatically.
-The value 0 is the default and means the database is closed when the last connection is closed.
-This setting is persistent and can be set by an administrator only.
-It is possible to set the value in the database URL: <code>jdbc:h2:~/test;DB_CLOSE_DELAY=10</code>.
-</p>
-
-<h3 id="do_not_close_on_exit">Don't Close a Database when the VM Exits</h3>
-<p>
-By default, a database is closed when the last connection is closed. However, if it is never closed,
-the database is closed when the virtual machine exits normally, using a shutdown hook.
-In some situations, the database should not be closed in this case, for example because the
-database is still used at virtual machine shutdown (to store the shutdown process in the database for example).
-For those cases, the automatic closing of the database can be disabled in the database URL.
-The first connection (the one that is opening the database) needs to
-set the option in the database URL (it is not possible to change the setting afterwards).
-The database URL to disable database closing on exit is:
-</p>
-<pre>
-String url = "jdbc:h2:~/test;DB_CLOSE_ON_EXIT=FALSE";
-</pre>
-
-<h2 id="execute_sql_on_connection">Execute SQL on Connection</h2>
-<p>
-Sometimes, particularly for in-memory databases, it is useful to be able to execute DDL or DML
-commands automatically when a client connects to a database. This functionality is enabled via
-the INIT property. Note that multiple commands may be passed to INIT, but the semicolon delimiter
-must be escaped, as in the example below.
-</p>
-<pre>
-String url = "jdbc:h2:mem:test;INIT=runscript from '~/create.sql'\\;runscript from '~/init.sql'";
-</pre>
-<p>
-Please note the double backslash is only required in a Java or properties file.
-In a GUI, or in an XML file, only one backslash is required:
-</p>
-<pre>
-<property name="url" value=
-"jdbc:h2:mem:test;INIT=create schema if not exists test\;runscript from '~/sql/init.sql'"
-/>
-</pre>
-<p>
-Backslashes within the init script (for example within a runscript statement, to specify the folder names in Windows)
-need to be escaped as well (using a second backslash). It might be simpler to avoid backslashes in folder names for this reason;
-use forward slashes instead.
-</p>
-
-<h2 id="ignore_unknown_settings">Ignore Unknown Settings</h2>
-<p>
-Some applications (for example OpenOffice.org Base) pass some additional parameters
-when connecting to the database. Why those parameters are passed is unknown.
-The parameters <code>PREFERDOSLIKELINEENDS</code> and
-<code>IGNOREDRIVERPRIVILEGES</code> are such examples;
-they are simply ignored to improve the compatibility with OpenOffice.org. If an application
-passes other parameters when connecting to the database, usually the database throws an exception
-saying the parameter is not supported. It is possible to ignored such parameters by adding
-<code>;IGNORE_UNKNOWN_SETTINGS=TRUE</code> to the database URL.
-</p>
-
-<h2 id="other_settings">Changing Other Settings when Opening a Connection</h2>
-<p>
-In addition to the settings already described,
-other database settings can be passed in the database URL.
-Adding <code>;setting=value</code> at the end of a database URL is the
-same as executing the statement <code>SET setting value</code> just after
-connecting. For a list of supported settings, see <a href="grammar.html">SQL Grammar</a>
-or the <a href="http://www.h2database.com/javadoc/org/h2/engine/DbSettings.html">DbSettings</a> javadoc.
-</p>
-
-<h2 id="custom_access_mode">Custom File Access Mode</h2>
-<p>
-Usually, the database opens the database file with the access mode
-<code>rw</code>, meaning read-write (except for read only databases,
-where the mode <code>r</code> is used).
-To open a database in read-only mode if the database file is not read-only, use
-<code>ACCESS_MODE_DATA=r</code>.
-Also supported are <code>rws</code> and <code>rwd</code>.
-This setting must be specified in the database URL:
-</p>
-<pre>
-String url = "jdbc:h2:~/test;ACCESS_MODE_DATA=rws";
-</pre>
-<p>
-For more information see <a href="advanced.html#durability_problems">Durability Problems</a>.
-On many operating systems the access mode <code>rws</code> does not guarantee that the data is written to the disk.
-</p>
-
-<h2 id="multiple_connections">Multiple Connections</h2>
-
-<h3>Opening Multiple Databases at the Same Time</h3>
-<p>
-An application can open multiple databases at the same time, including multiple
-connections to the same database. The number of open database is only limited by the memory available.
-</p>
-
-<h3>Multiple Connections to the Same Database: Client/Server</h3>
-<p>
-If you want to access the same database at the same time from different processes or computers,
-you need to use the client / server mode. In this case, one process acts as the server, and the
-other processes (that could reside on other computers as well) connect to the server via TCP/IP
-(or TLS over TCP/IP for improved security).
-</p>
-
-<h3>Multithreading Support</h3>
-<p>
-This database is multithreading-safe.
-If an application is multi-threaded, it does not need to worry about synchronizing access to the database.
-An application should normally use one connection per thread.
-This database synchronizes access to the same connection, but other databases may not do this.
-To get higher concurrency, you need to use multiple connections.
-</p>
-<p>
-An application can use multiple threads that access the same database at the same time.
-With default MVStore engine threads that use different connections can use the database concurrently.
-With PageStore engine requests to the same database are synchronized,
-that means that if one thread executes a long running query, the other threads need to wait.
-Concurrent database usage may be enabled for PageStore or disabled for MVStore
-with <code>MULTI_THREADED</code> setting.
-Note that multi-threaded mode for PageStore engine is not tested well and has some issues;
-it should be used with caution.
-</p>
-
-<h3>Locking, Lock-Timeout, Deadlocks</h3>
-<p>
-Please note MVCC is enabled in version 1.4.x by default, when using the MVStore.
-In this case, table level locking is not used.
-
-If <a href="advanced.html#mvcc">multi-version concurrency</a> is not used,
-the database uses table level locks to give each connection a consistent state of the data.
-There are two kinds of locks: read locks (shared locks) and write locks (exclusive locks).
-All locks are released when the transaction commits or rolls back.
-When using the default transaction isolation level 'read committed', read locks are already released after each statement.
-</p><p>
-If a connection wants to reads from a table, and there is no write lock on the table,
-then a read lock is added to the table. If there is a write lock, then this connection waits
-for the other connection to release the lock. If a connection cannot get a lock for a specified time,
-then a lock timeout exception is thrown.
-</p><p>
-Usually, <code>SELECT</code> statements will generate read locks. This includes subqueries.
-Statements that modify data use write locks. It is also possible to lock a table exclusively without modifying data,
-using the statement <code>SELECT ... FOR UPDATE</code>.
-The statements <code>COMMIT</code> and
-<code>ROLLBACK</code> releases all open locks.
-The commands <code>SAVEPOINT</code> and
-<code>ROLLBACK TO SAVEPOINT</code> don't affect locks.
-The locks are also released when the autocommit mode changes, and for connections with
-autocommit set to true (this is the default), locks are released after each statement.
-The following statements generate locks:
-</p>
-<table class="main">
- <tr>
- <th>Type of Lock</th>
- <th>SQL Statement</th>
- </tr>
- <tr>
- <td>Read</td>
- <td class="notranslate">SELECT * FROM TEST;<br />
- CALL SELECT MAX(ID) FROM TEST;<br />
- SCRIPT;</td>
- </tr>
- <tr>
- <td>Write</td>
- <td class="notranslate">SELECT * FROM TEST WHERE 1=0 FOR UPDATE;</td>
- </tr>
- <tr>
- <td>Write</td>
- <td class="notranslate">INSERT INTO TEST VALUES(1, 'Hello');<br />
- INSERT INTO TEST SELECT * FROM TEST;<br />
- UPDATE TEST SET NAME='Hi';<br />
- DELETE FROM TEST;</td>
- </tr>
- <tr>
- <td>Write</td>
- <td class="notranslate">ALTER TABLE TEST ...;<br />
- CREATE INDEX ... ON TEST ...;<br />
- DROP INDEX ...;</td>
- </tr>
-</table>
-<p>
-The number of seconds until a lock timeout exception is thrown can be
-set separately for each connection using the SQL command
-<code>SET LOCK_TIMEOUT <milliseconds></code>.
-The initial lock timeout (that is the timeout used for new connections) can be set using the SQL command
-<code>SET DEFAULT_LOCK_TIMEOUT <milliseconds></code>. The default lock timeout is persistent.
-</p>
-
-<h3>Avoiding Deadlocks</h3>
-<p>
-To avoid deadlocks, ensure that all transactions lock the tables in the same order
-(for example in alphabetical order), and avoid upgrading read locks to write locks.
-Both can be achieved using explicitly locking tables using <code>SELECT ... FOR UPDATE</code>.
-</p><p>
-Note that delete, insert and update operations issue table level locks with PageStore engine,
-but does not issue them with default MVStore engine.
-</p>
-
-<h2 id="database_file_layout">Database File Layout</h2>
-<p>
-The following files are created for persistent databases:
-</p>
-<table class="main">
-<tr><th>File Name</th><th>Description</th><th>Number of Files</th></tr>
-<tr><td class="notranslate">
- test.h2.db
-</td><td>
- Database file.<br />
- Contains the transaction log, indexes, and data for all tables.<br />
- Format: <code><database>.h2.db</code>
-</td><td>
- 1 per database
-</td></tr>
-<tr><td class="notranslate">
- test.lock.db
-</td><td>
- Database lock file.<br />
- Automatically (re-)created while the database is in use.<br />
- Format: <code><database>.lock.db</code>
-</td><td>
- 1 per database (only if in use)
-</td></tr>
-<tr><td class="notranslate">
- test.trace.db
-</td><td>
- Trace file (if the trace option is enabled).<br />
- Contains trace information.<br />
- Format: <code><database>.trace.db</code><br />
- Renamed to <code><database>.trace.db.old</code> is too big.
-</td><td>
- 0 or 1 per database
-</td></tr>
-<tr><td class="notranslate">
- test.lobs.db/*
-</td><td>
- Directory containing one file for each<br />
- BLOB or CLOB value larger than a certain size.<br />
- Format: <code><id>.t<tableId>.lob.db</code>
-</td><td>
- 1 per large object
-</td></tr>
-<tr><td class="notranslate">
- test.123.temp.db
-</td><td>
- Temporary file.<br />
- Contains a temporary blob or a large result set.<br />
- Format: <code><database>.<id>.temp.db</code>
-</td><td>
- 1 per object
-</td></tr>
-</table>
-
-<h3>Moving and Renaming Database Files</h3>
-<p>
-Database name and location are not stored inside the database files.
-</p><p>
-While a database is closed, the files can be moved to another directory, and they can
-be renamed as well (as long as all files of the same database start with the same
-name and the respective extensions are unchanged).
-</p><p>
-As there is no platform specific data in the files, they can be moved to other operating systems
-without problems.
-</p>
-
-<h3>Backup</h3>
-<p>
-When the database is closed, it is possible to backup the database files.
-</p><p>
-To backup data while the database is running,
-the SQL commands <code>SCRIPT</code> and <code>BACKUP</code> can be used.
-</p>
-
-<h2 id="logging_recovery">Logging and Recovery</h2>
-<p>
-Whenever data is modified in the database and those changes are committed, the changes are written
-to the transaction log (except for in-memory objects). The changes to the main data area itself are usually written
-later on, to optimize disk access. If there is a power failure, the main data area is not up-to-date,
-but because the changes are in the transaction log, the next time the database is opened, the changes
-are re-applied automatically.
-</p>
-
-<h2 id="compatibility">Compatibility</h2>
-<p>
-All database engines behave a little bit different. Where possible, H2 supports the ANSI SQL standard,
-and tries to be compatible to other databases. There are still a few differences however:
-</p>
-<p>
-In MySQL text columns are case insensitive by default, while in H2 they are case sensitive. However
-H2 supports case insensitive columns as well. To create the tables with case insensitive texts, append
-<code>IGNORECASE=TRUE</code> to the database URL
-(example: <code>jdbc:h2:~/test;IGNORECASE=TRUE</code>).
-</p>
-
-<h3>Compatibility Modes</h3>
-<p>
-For certain features, this database can emulate the behavior of specific databases.
-However, only a small subset of the differences between databases are implemented in this way.
-Here is the list of currently supported modes and the differences to the regular mode:
-</p>
-
-<h3>DB2 Compatibility Mode</h3>
-<p>
-To use the IBM DB2 mode, use the database URL <code>jdbc:h2:~/test;MODE=DB2</code>
-or the SQL statement <code>SET MODE DB2</code>.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>Concatenating <code>NULL</code> with another value
- results in the other value.
-</li><li>Support the pseudo-table SYSIBM.SYSDUMMY1.
-</li><li>Timestamps with dash between date and time are supported.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-
-<h3>Derby Compatibility Mode</h3>
-<p>
-To use the Apache Derby mode, use the database URL <code>jdbc:h2:~/test;MODE=Derby</code>
-or the SQL statement <code>SET MODE Derby</code>.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>For unique indexes, <code>NULL</code> is distinct.
- That means only one row with <code>NULL</code> in one of the columns is allowed.
-</li><li>Concatenating <code>NULL</code> with another value
- results in the other value.
-</li><li>Support the pseudo-table SYSIBM.SYSDUMMY1.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-
-<h3>HSQLDB Compatibility Mode</h3>
-<p>
-To use the HSQLDB mode, use the database URL <code>jdbc:h2:~/test;MODE=HSQLDB</code>
-or the SQL statement <code>SET MODE HSQLDB</code>.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>When converting the scale of decimal data, the number is only converted if the new scale is
- smaller than the current scale. Usually, the scale is converted and 0s are added if required.
-</li><li>For unique indexes, <code>NULL</code> is distinct.
- That means only one row with <code>NULL</code> in one of the columns is allowed.
-</li><li>Text can be concatenated using '+'.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-
-<h3>MS SQL Server Compatibility Mode</h3>
-<p>
-To use the MS SQL Server mode, use the database URL <code>jdbc:h2:~/test;MODE=MSSQLServer</code>
-or the SQL statement <code>SET MODE MSSQLServer</code>.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>Identifiers may be quoted using square brackets as in <code>[Test]</code>.
-</li><li>For unique indexes, <code>NULL</code> is distinct.
- That means only one row with <code>NULL</code> in one of the columns is allowed.
-</li><li>Concatenating <code>NULL</code> with another value
- results in the other value.
-</li><li>Text can be concatenated using '+'.
-</li><li>MONEY data type is treated like NUMERIC(19, 4) data type. SMALLMONEY data type is treated like NUMERIC(10, 4)
- data type.
-</li><li><code>IDENTITY</code> can be used for automatic id generation on column level.
-</li><li>Table hints are discarded. Example: <code>SELECT * FROM table WITH (NOLOCK)</code>.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-
-<h3>MySQL Compatibility Mode</h3>
-<p>
-To use the MySQL mode, use the database URL <code>jdbc:h2:~/test;MODE=MySQL;DATABASE_TO_LOWER=TRUE</code>.
-Use this mode for compatibility with MariaDB too.
-When case-insensitive identifiers are needed append <code>;CASE_INSENSITIVE_IDENTIFIERS=TRUE</code> to URL.
-Do not change value of DATABASE_TO_LOWER after creation of database.
-</p>
-<ul><li>When inserting data, if a column is defined to be <code>NOT NULL</code>
- and <code>NULL</code> is inserted,
- then a 0 (or empty string, or the current timestamp for timestamp columns) value is used.
- Usually, this operation is not allowed and an exception is thrown.
-</li><li>Creating indexes in the <code>CREATE TABLE</code> statement is allowed using
- <code>INDEX(..)</code> or <code>KEY(..)</code>.
- Example: <code>create table test(id int primary key, name varchar(255), key idx_name(name));</code>
-</li><li>When converting a floating point number to an integer, the fractional
- digits are not truncated, but the value is rounded.
-</li><li>Concatenating <code>NULL</code> with another value
- results in the other value.
-</li><li>ON DUPLICATE KEY UPDATE is supported in INSERT statements, due to this feature VALUES has special non-standard
- meaning is some contexts.
-</li><li>INSERT IGNORE is partially supported and may be used to skip rows with duplicate keys if ON DUPLICATE KEY
- UPDATE is not specified.
-</li><li>REGEXP_REPLACE() uses \ for back-references for compatibility with MariaDB.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-<p>
-Text comparison in MySQL is case insensitive by default, while in H2 it is case sensitive (as in most other databases).
-H2 does support case insensitive text comparison, but it needs to be set separately,
-using <code>SET IGNORECASE TRUE</code>.
-This affects comparison using <code>=, LIKE, REGEXP</code>.
-</p>
-
-<h3>Oracle Compatibility Mode</h3>
-<p>
-To use the Oracle mode, use the database URL <code>jdbc:h2:~/test;MODE=Oracle</code>
-or the SQL statement <code>SET MODE Oracle</code>.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>When using unique indexes, multiple rows with <code>NULL</code>
- in all columns are allowed, however it is not allowed to have multiple rows with the
- same values otherwise.
-</li><li>Concatenating <code>NULL</code> with another value
- results in the other value.
-</li><li>Empty strings are treated like <code>NULL</code> values.
-</li><li>REGEXP_REPLACE() uses \ for back-references.
-</li><li>DATE data type is treated like TIMESTAMP(0) data type.
-</li><li>Datetime value functions return the same value within a command.
-</li></ul>
-
-<h3>PostgreSQL Compatibility Mode</h3>
-<p>
-To use the PostgreSQL mode, use the database URL <code>jdbc:h2:~/test;MODE=PostgreSQL;DATABASE_TO_LOWER=TRUE</code>.
-Do not change value of DATABASE_TO_LOWER after creation of database.
-</p>
-<ul><li>For aliased columns, <code>ResultSetMetaData.getColumnName()</code>
- returns the alias name and <code>getTableName()</code> returns
- <code>null</code>.
-</li><li>When converting a floating point number to an integer, the fractional
- digits are not be truncated, but the value is rounded.
-</li><li>The system columns <code>CTID</code> and
- <code>OID</code> are supported.
-</li><li>LOG(x) is base 10 in this mode.
-</li><li>REGEXP_REPLACE():
- <ul>
- <li>uses \ for back-references;</li>
- <li>does not throw an exception when the <code>flagsString</code> parameter contains a 'g';</li>
- <li>replaces only the first matched substring in the absence of the 'g' flag in the <code>flagsString</code> parameter.</li>
- </ul>
-</li><li>Fixed-width strings are padded with spaces.
-</li><li>MONEY data type is treated like NUMERIC(19, 2) data type.
-</li><li>Datetime value functions return the same value within a transaction.
-</li><li>ARRAY_SLICE() out of bounds parameters are silently corrected.
-</li><li>EXTRACT function with DOW field returns (0-6), Sunday is 0.
-</li></ul>
-
-<h3>Ignite Compatibility Mode</h3>
-<p>
-To use the Ignite mode, use the database URL <code>jdbc:h2:~/test;MODE=Ignite</code>
-or the SQL statement <code>SET MODE Ignite</code>.
-</p>
-<ul><li>Creating indexes in the <code>CREATE TABLE</code> statement is allowed using
- <code>INDEX(..)</code> or <code>KEY(..)</code>.
- Example: <code>create table test(id int primary key, name varchar(255), key idx_name(name));</code>
-</li><li>AFFINITY KEY and SHARD KEY keywords may be used in index definition.
-</li><li>Datetime value functions return the same value within a transaction.
-</li></ul>
-
-<h2 id="auto_reconnect">Auto-Reconnect</h2>
-<p>
-The auto-reconnect feature causes the JDBC driver to reconnect to
-the database if the connection is lost. The automatic re-connect only
-occurs when auto-commit is enabled; if auto-commit is disabled, an exception is thrown.
-To enable this mode, append <code>;AUTO_RECONNECT=TRUE</code> to the database URL.
-</p>
-<p>
-Re-connecting will open a new session. After an automatic re-connect,
-variables and local temporary tables definitions (excluding data) are re-created.
-The contents of the system table <code>INFORMATION_SCHEMA.SESSION_STATE</code>
-contains all client side state that is re-created.
-</p>
-<p>
-If another connection uses the database in exclusive mode (enabled using <code>SET EXCLUSIVE 1</code>
-or <code>SET EXCLUSIVE 2</code>), then this connection will try to re-connect until the exclusive mode ends.
-</p>
-
-<h2 id="auto_mixed_mode">Automatic Mixed Mode</h2>
-<p>
-Multiple processes can access the same database without having to start the server manually.
-To do that, append <code>;AUTO_SERVER=TRUE</code> to the database URL.
-You can use the same database URL independent of whether the database is already open or not.
-This feature doesn't work with in-memory databases. Example database URL:
-</p>
-<pre>
-jdbc:h2:/data/test;AUTO_SERVER=TRUE
-</pre>
-<p>
-Use the same URL for all connections to this database. Internally, when using this mode,
-the first connection to the database is made in embedded mode, and additionally a server
-is started internally (as a daemon thread). If the database is already open in another process,
-the server mode is used automatically. The IP address and port of the server are stored in the file
-<code>.lock.db</code>, that's why in-memory databases can't be supported.
-</p>
-<p>
-The application that opens the first connection to the database uses the embedded mode,
-which is faster than the server mode. Therefore the main application should open
-the database first if possible. The first connection automatically starts a server on a random port.
-This server allows remote connections, however only to this database (to ensure that,
-the client reads <code>.lock.db</code> file and sends the random key that is stored there to the server).
-When the first connection is closed, the server stops. If other (remote) connections are still
-open, one of them will then start a server (auto-reconnect is enabled automatically).
-</p>
-<p>
-All processes need to have access to the database files.
-If the first connection is closed (the connection that started the server), open transactions of other connections will be rolled back
-(this may not be a problem if you don't disable autocommit).
-Explicit client/server connections (using <code>jdbc:h2:tcp://</code> or <code>ssl://</code>) are not supported.
-This mode is not supported for in-memory databases.
-</p>
-<p>
-Here is an example how to use this mode. Application 1 and 2 are not necessarily started
-on the same computer, but they need to have access to the database files. Application 1
-and 2 are typically two different processes (however they could run within the same process).
-</p>
-<pre>
-// Application 1:
-DriverManager.getConnection("jdbc:h2:/data/test;AUTO_SERVER=TRUE");
-
-// Application 2:
-DriverManager.getConnection("jdbc:h2:/data/test;AUTO_SERVER=TRUE");
-</pre>
-<p>
-When using this feature, by default the server uses any free TCP port.
-The port can be set manually using <code>AUTO_SERVER_PORT=9090</code>.
-</p>
-
-<h2 id="page_size">Page Size</h2>
-<p>
-The page size for new databases is 2 KB (2048), unless the page size is set
-explicitly in the database URL using <code>PAGE_SIZE=</code> when
-the database is created. The page size of existing databases can not be changed,
-so this property needs to be set when the database is created.
-</p>
-
-<h2 id="trace_options">Using the Trace Options</h2>
-<p>
-To find problems in an application, it is sometimes good to see what database operations
-where executed. This database offers the following trace features:
-</p>
-<ul>
-<li>Trace to <code>System.out</code> and/or to a file
-</li><li>Support for trace levels <code>OFF, ERROR, INFO, DEBUG</code>
-</li><li>The maximum size of the trace file can be set
-</li><li>It is possible to generate Java source code from the trace file
-</li><li>Trace can be enabled at runtime by manually creating a file
-</li></ul>
-
-<h3>Trace Options</h3>
-<p>
-The simplest way to enable the trace option is setting it in the database URL.
-There are two settings, one for <code>System.out</code>
-(<code>TRACE_LEVEL_SYSTEM_OUT</code>) tracing,
-and one for file tracing (<code>TRACE_LEVEL_FILE</code>).
-The trace levels are
-0 for <code>OFF</code>,
-1 for <code>ERROR</code> (the default),
-2 for <code>INFO</code>, and
-3 for <code>DEBUG</code>.
-A database URL with both levels set to <code>DEBUG</code> is:
-</p>
-<pre>
-jdbc:h2:~/test;TRACE_LEVEL_FILE=3;TRACE_LEVEL_SYSTEM_OUT=3
-</pre>
-<p>
-The trace level can be changed at runtime by executing the SQL command
-<code>SET TRACE_LEVEL_SYSTEM_OUT level</code> (for <code>System.out</code> tracing)
-or <code>SET TRACE_LEVEL_FILE level</code> (for file tracing).
-Example:
-</p>
-<pre>
-SET TRACE_LEVEL_SYSTEM_OUT 3
-</pre>
-
-<h3>Setting the Maximum Size of the Trace File</h3>
-<p>
-When using a high trace level, the trace file can get very big quickly.
-The default size limit is 16 MB, if the trace file exceeds this limit, it is renamed to
-<code>.old</code> and a new file is created.
-If another such file exists, it is deleted.
-To limit the size to a certain number of megabytes, use
-<code>SET TRACE_MAX_FILE_SIZE mb</code>.
-Example:
-</p>
-<pre>
-SET TRACE_MAX_FILE_SIZE 1
-</pre>
-
-<h3>Java Code Generation</h3>
-<p>
-When setting the trace level to <code>INFO</code> or <code>DEBUG</code>,
-Java source code is generated as well. This simplifies reproducing problems. The trace file looks like this:
-</p>
-<pre>
-...
-12-20 20:58:09 jdbc[0]:
-/**/dbMeta3.getURL();
-12-20 20:58:09 jdbc[0]:
-/**/dbMeta3.getTables(null, "", null, new String[]{"TABLE", "VIEW"});
-...
-</pre>
-<p>
-To filter the Java source code, use the <code>ConvertTraceFile</code> tool as follows:
-</p>
-<pre>
-java -cp h2*.jar org.h2.tools.ConvertTraceFile
- -traceFile "~/test.trace.db" -javaClass "Test"
-</pre>
-<p>
-The generated file <code>Test.java</code> will contain the Java source code.
-The generated source code may be too large to compile (the size of a Java method is limited).
-If this is the case, the source code needs to be split in multiple methods.
-The password is not listed in the trace file and therefore not included in the source code.
-</p>
-
-<h2 id="other_logging">Using Other Logging APIs</h2>
-<p>
-By default, this database uses its own native 'trace' facility. This facility is called 'trace' and not
-'log' within this database to avoid confusion with the transaction log. Trace messages can be
-written to both file and <code>System.out</code>.
-In most cases, this is sufficient, however sometimes it is better to use the same
-facility as the application, for example Log4j. To do that, this database support SLF4J.
-</p>
-<p>
-<a href="https://www.slf4j.org/">SLF4J</a> is a simple facade for various logging APIs
-and allows to plug in the desired implementation at deployment time.
-SLF4J supports implementations such as Logback, Log4j, Jakarta Commons Logging (JCL),
-Java logging, x4juli, and Simple Log.
-</p>
-<p>
-To enable SLF4J, set the file trace level to 4 in the database URL:
-</p>
-<pre>
-jdbc:h2:~/test;TRACE_LEVEL_FILE=4
-</pre>
-<p>
-Changing the log mechanism is not possible after the database is open, that means
-executing the SQL statement <code>SET TRACE_LEVEL_FILE 4</code>
-when the database is already open will not have the desired effect.
-To use SLF4J, all required jar files need to be in the classpath.
-The logger name is <code>h2database</code>.
-If it does not work, check the file <code><database>.trace.db</code> for error messages.
-</p>
-
-<h2 id="read_only">Read Only Databases</h2>
-<p>
-If the database files are read-only, then the database is read-only as well.
-It is not possible to create new tables, add or modify data in this database.
-Only <code>SELECT</code> and <code>CALL</code> statements are allowed.
-To create a read-only database, close the database.
-Then, make the database file read-only.
-When you open the database now, it is read-only.
-There are two ways an application can find out whether database is read-only:
-by calling <code>Connection.isReadOnly()</code>
-or by executing the SQL statement <code>CALL READONLY()</code>.
-</p>
-<p>
-Using the <a href="#custom_access_mode">Custom Access Mode</a> <code>r</code>
-the database can also be opened in read-only mode, even if the database file is not read only.
-</p>
-
-<h2 id="database_in_zip">Read Only Databases in Zip or Jar File</h2>
-<p>
-To create a read-only database in a zip file, first create a regular persistent database, and then create a backup.
-The database must not have pending changes, that means you need to close all connections to the database first.
-To speed up opening the read-only database and running queries, the database should be closed using <code>SHUTDOWN DEFRAG</code>.
-If you are using a database named <code>test</code>, an easy way to create a zip file is using the
-<code>Backup</code> tool. You can start the tool from the command line, or from within the
-H2 Console (Tools - Backup). Please note that the database must be closed when the backup
-is created. Therefore, the SQL statement <code>BACKUP TO</code> can not be used.
-</p>
-<p>
-When the zip file is created, you can open the database in the zip file using the following database URL:
-</p>
-<pre>
-jdbc:h2:zip:~/data.zip!/test
-</pre>
-<p>
-Databases in zip files are read-only. The performance for some queries will be slower than when using
-a regular database, because random access in zip files is not supported (only streaming). How much this
-affects the performance depends on the queries and the data. The database
-is not read in memory; therefore large databases are supported as well. The same indexes are used as when using
-a regular database.
-</p>
-<p>
-If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files,
-because random access in compressed files is not possible.
-See also the sample application <a href="https://github.com/h2database/h2database/tree/master/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
-</p>
-
-<h3>Opening a Corrupted Database</h3>
-<p>
-If a database cannot be opened because the boot info (the SQL script that is run at startup)
-is corrupted, then the database can be opened by specifying a database event listener.
-The exceptions are logged, but opening the database will continue.
-</p>
-
-<h2 id="computed_columns">Computed Columns / Function Based Index</h2>
-<p>
-A computed column is a column whose value is calculated before storing.
-The formula is evaluated when the row is inserted, and re-evaluated every time the row is updated.
-One use case is to automatically update the last-modification time:
-</p>
-<pre>
-CREATE TABLE TEST(ID INT, NAME VARCHAR, LAST_MOD TIMESTAMP AS NOW());
-</pre>
-<p>
-Function indexes are not directly supported by this database, but they can be emulated
-by using computed columns. For example, if an index on the upper-case version of
-a column is required, create a computed column with the upper-case version of the original column,
-and create an index for this column:
-</p>
-<pre>
-CREATE TABLE ADDRESS(
- ID INT PRIMARY KEY,
- NAME VARCHAR,
- UPPER_NAME VARCHAR AS UPPER(NAME)
-);
-CREATE INDEX IDX_U_NAME ON ADDRESS(UPPER_NAME);
-</pre>
-<p>
-When inserting data, it is not required (and not allowed) to specify a value for the upper-case
-version of the column, because the value is generated. But you can use the
-column when querying the table:
-</p>
-<pre>
-INSERT INTO ADDRESS(ID, NAME) VALUES(1, 'Miller');
-SELECT * FROM ADDRESS WHERE UPPER_NAME='MILLER';
-</pre>
-
-<h2 id="multi_dimensional">Multi-Dimensional Indexes</h2>
-<p>
-A tool is provided to execute efficient multi-dimension (spatial) range queries.
-This database does not support a specialized spatial index (R-Tree or similar).
-Instead, the B-Tree index is used. For each record, the multi-dimensional key
-is converted (mapped) to a single dimensional (scalar) value.
-This value specifies the location on a space-filling curve.
-</p><p>
-Currently, Z-order (also called N-order or Morton-order) is used;
-Hilbert curve could also be used, but the implementation is more complex.
-The algorithm to convert the multi-dimensional value is called bit-interleaving.
-The scalar value is indexed using a B-Tree index (usually using a computed column).
-</p><p>
-The method can result in a drastic performance improvement
-over just using an index on the first column. Depending on the
-data and number of dimensions, the improvement is usually higher than factor 5.
-The tool generates a SQL query from a specified multi-dimensional range.
-The method used is not database dependent, and the tool can easily be ported to other databases.
-For an example how to use the tool, please have a look at the sample code provided
-in <code>TestMultiDimension.java</code>.
-</p>
-
-<h2 id="user_defined_functions">User-Defined Functions and Stored Procedures</h2>
-<p>
-In addition to the built-in functions, this database supports user-defined Java functions.
-In this database, Java functions can be used as stored procedures as well.
-A function must be declared (registered) before it can be used.
-A function can be defined using source code, or as a reference to
-a compiled class that is available in the classpath. By default, the
-function aliases are stored in the current schema.
-</p>
-
-<h3>Referencing a Compiled Method</h3>
-<p>
-When referencing a method, the class must already be compiled and
-included in the classpath where the database is running.
-Only static Java methods are supported; both the class and the method must be public.
-Example Java class:
-</p>
-<pre>
-package acme;
-import java.math.*;
-public class Function {
- public static boolean isPrime(int value) {
- return new BigInteger(String.valueOf(value)).isProbablePrime(100);
- }
-}
-</pre>
-<p>
-The Java function must be registered in the database by calling <code>CREATE ALIAS ... FOR</code>:
-</p>
-<pre>
-CREATE ALIAS IS_PRIME FOR "acme.Function.isPrime";
-</pre>
-<p>
-For a complete sample application, see <code>src/test/org/h2/samples/Function.java</code>.
-</p>
-
-<h3>Declaring Functions as Source Code</h3>
-<p>
-When defining a function alias with source code, the database tries to compile
-the source code using the Sun Java compiler (the class <code>com.sun.tools.javac.Main</code>)
-if the <code>tools.jar</code> is in the classpath. If not, <code>javac</code> is run as a separate process.
-Only the source code is stored in the database; the class is compiled each time the database is re-opened.
-Source code is usually passed as dollar quoted text to avoid escaping problems, however single quotes can be used as well.
-Example:
-</p>
-<pre>
-CREATE ALIAS NEXT_PRIME AS $$
-String nextPrime(String value) {
- return new BigInteger(value).nextProbablePrime().toString();
-}
-$$;
-</pre>
-<p>
-By default, the three packages <code>java.util, java.math, java.sql</code> are imported.
-The method name (<code>nextPrime</code> in the example above) is ignored.
-Method overloading is not supported when declaring functions as source code, that means only one method may be declared for an alias.
-If different import statements are required, they must be declared at the beginning
-and separated with the tag <code>@CODE</code>:
-</p>
-<pre>
-CREATE ALIAS IP_ADDRESS AS $$
-import java.net.*;
-@CODE
-String ipAddress(String host) throws Exception {
- return InetAddress.getByName(host).getHostAddress();
-}
-$$;
-</pre>
-<p>
-The following template is used to create a complete Java class:
-</p>
-<pre>
-package org.h2.dynamic;
-< import statements before the tag @CODE; if not set:
-import java.util.*;
-import java.math.*;
-import java.sql.*;
->
-public class <aliasName> {
- public static <sourceCode>
-}
-</pre>
-
-<h3>Method Overloading</h3>
-<p>
-Multiple methods may be bound to a SQL function if the class is already compiled and included in the classpath.
-Each Java method must have a different number of arguments.
-Method overloading is not supported when declaring functions as source code.
-</p>
-
-<h3>Function Data Type Mapping</h3>
-<p>
-Functions that accept non-nullable parameters such as <code>int</code>
-will not be called if one of those parameters is <code>NULL</code>.
-Instead, the result of the function is <code>NULL</code>.
-If the function should be called if a parameter is <code>NULL</code>, you need
-to use <code>java.lang.Integer</code> instead.
-</p>
-<p>
-SQL types are mapped to Java classes and vice-versa as in the JDBC API. For details, see <a href="datatypes.html">Data Types</a>.
-There are a few special cases: <code>java.lang.Object</code> is mapped to
-<code>OTHER</code> (a serialized object). Therefore,
-<code>java.lang.Object</code> can not be used
-to match all SQL types (matching all SQL types is not supported). The second special case is <code>Object[]</code>:
-arrays of any class are mapped to <code>ARRAY</code>.
-Objects of type <code>org.h2.value.Value</code> (the internal value class) are passed through without conversion.
-</p>
-
-<h3>Functions That Require a Connection</h3>
-<p>
-If the first parameter of a Java function is a <code>java.sql.Connection</code>, then the connection
-to database is provided. This connection does not need to be closed before returning.
-When calling the method from within the SQL statement, this connection parameter
-does not need to be (can not be) specified.
-</p>
-
-<h3>Functions Throwing an Exception</h3>
-<p>
-If a function throws an exception, then the current statement is rolled back
-and the exception is thrown to the application.
-SQLException are directly re-thrown to the calling application;
-all other exceptions are first converted to a SQLException.
-</p>
-
-<h3>Functions Returning a Result Set</h3>
-<p>
-Functions may returns a result set. Such a function can be called with the <code>CALL</code> statement:
-</p>
-<pre>
-public static ResultSet query(Connection conn, String sql) throws SQLException {
- return conn.createStatement().executeQuery(sql);
-}
-
-CREATE ALIAS QUERY FOR "org.h2.samples.Function.query";
-CALL QUERY('SELECT * FROM TEST');
-</pre>
-
-<h3>Using SimpleResultSet</h3>
-<p>
-A function can create a result set using the <code>SimpleResultSet</code> tool:
-</p>
-<pre>
-import org.h2.tools.SimpleResultSet;
-...
-public static ResultSet simpleResultSet() throws SQLException {
- SimpleResultSet rs = new SimpleResultSet();
- rs.addColumn("ID", Types.INTEGER, 10, 0);
- rs.addColumn("NAME", Types.VARCHAR, 255, 0);
- rs.addRow(0, "Hello");
- rs.addRow(1, "World");
- return rs;
-}
-
-CREATE ALIAS SIMPLE FOR "org.h2.samples.Function.simpleResultSet";
-CALL SIMPLE();
-</pre>
-
-<h3>Using a Function as a Table</h3>
-<p>
-A function that returns a result set can be used like a table.
-However, in this case the function is called at least twice:
-first while parsing the statement to collect the column names
-(with parameters set to <code>null</code> where not known at compile time).
-And then, while executing the statement to get the data (maybe multiple times if this is a join).
-If the function is called just to get the column list, the URL of the connection passed to the function is
-<code>jdbc:columnlist:connection</code>. Otherwise, the URL of the connection is
-<code>jdbc:default:connection</code>.
-</p>
-<pre>
-public static ResultSet getMatrix(Connection conn, Integer size)
- throws SQLException {
- SimpleResultSet rs = new SimpleResultSet();
- rs.addColumn("X", Types.INTEGER, 10, 0);
- rs.addColumn("Y", Types.INTEGER, 10, 0);
- String url = conn.getMetaData().getURL();
- if (url.equals("jdbc:columnlist:connection")) {
- return rs;
- }
- for (int s = size.intValue(), x = 0; x < s; x++) {
- for (int y = 0; y < s; y++) {
- rs.addRow(x, y);
- }
- }
- return rs;
-}
-
-CREATE ALIAS MATRIX FOR "org.h2.samples.Function.getMatrix";
-SELECT * FROM MATRIX(4) ORDER BY X, Y;
-</pre>
-
-
-<h2 id="pluggable_tables">Pluggable or User-Defined Tables</h2>
-<p>
-For situations where you need to expose other data-sources to the SQL engine as a table,
-there are "pluggable tables".
-For some examples, have a look at the code in <code>org.h2.test.db.TestTableEngines</code>.
-</p>
-<p>
-In order to create your own TableEngine, you need to implement the <code>org.h2.api.TableEngine</code> interface e.g.
-something like this:
-</p>
-<pre>
-package acme;
-public static class MyTableEngine implements org.h2.api.TableEngine {
-
- private static class MyTable extends org.h2.table.TableBase {
- .. rather a lot of code here...
- }
-
- public EndlessTable createTable(CreateTableData data) {
- return new EndlessTable(data);
- }
-}
-</pre>
-<p>
-and then create the table from SQL like this:
-</p>
-<pre>
-CREATE TABLE TEST(ID INT, NAME VARCHAR)
- ENGINE "acme.MyTableEngine";
-</pre>
-<p>
-It is also possible to pass in parameters to the table engine, like so:
-</p>
-<pre>
-CREATE TABLE TEST(ID INT, NAME VARCHAR) ENGINE "acme.MyTableEngine" WITH "param1", "param2";
-</pre>
-<p>
-In which case the parameters are passed down in the tableEngineParams field of the CreateTableData object.
-</p>
-<p>
-It is also possible to specify default table engine params on schema creation:
-</p>
-<pre>
-CREATE SCHEMA TEST_SCHEMA WITH "param1", "param2";
-</pre>
-<p>
-Params from the schema are used when CREATE TABLE issued on this schema does not have its own engine params specified.
-</p>
-
-<h2 id="triggers">Triggers</h2>
-<p>
-This database supports Java triggers that are called before or after a row is updated, inserted or deleted.
-Triggers can be used for complex consistency checks, or to update related data in the database.
-It is also possible to use triggers to simulate materialized views.
-For a complete sample application, see <code>src/test/org/h2/samples/TriggerSample.java</code>.
-A Java trigger must implement the interface <code>org.h2.api.Trigger</code>. The trigger class must be available
-in the classpath of the database engine (when using the server mode, it must be in the classpath
-of the server).
-</p>
-<pre>
-import org.h2.api.Trigger;
-...
-public class TriggerSample implements Trigger {
-
- public void init(Connection conn, String schemaName, String triggerName,
- String tableName, boolean before, int type) {
- // initialize the trigger object is necessary
- }
-
- public void fire(Connection conn,
- Object[] oldRow, Object[] newRow)
- throws SQLException {
- // the trigger is fired
- }
-
- public void close() {
- // the database is closed
- }
-
- public void remove() {
- // the trigger was dropped
- }
-
-}
-</pre>
-<p>
-The connection can be used to query or update data in other tables.
-The trigger then needs to be defined in the database:
-</p>
-<pre>
-CREATE TRIGGER INV_INS AFTER INSERT ON INVOICE
- FOR EACH ROW CALL "org.h2.samples.TriggerSample"
-</pre>
-<p>
-The trigger can be used to veto a change by throwing a <code>SQLException</code>.
-</p>
-<p>
-As an alternative to implementing the <code>Trigger</code> interface,
-an application can extend the abstract class <code>org.h2.tools.TriggerAdapter</code>.
-This will allows to use the <code>ResultSet</code> interface within trigger implementations.
-In this case, only the <code>fire</code> method needs to be implemented:
-</p>
-<pre>
-import org.h2.tools.TriggerAdapter;
-...
-public class TriggerSample extends TriggerAdapter {
-
- public void fire(Connection conn, ResultSet oldRow, ResultSet newRow)
- throws SQLException {
- // the trigger is fired
- }
-
-}
-</pre>
-
-<h2 id="compacting">Compacting a Database</h2>
-<p>
-Empty space in the database file re-used automatically. When closing the database,
-the database is automatically compacted for up to 200 milliseconds by default. To compact more,
-use the SQL statement SHUTDOWN COMPACT. However re-creating the database may further
-reduce the database size because this will re-build the indexes.
-Here is a sample function to do this:
-</p>
-<pre>
-public static void compact(String dir, String dbName,
- String user, String password) throws Exception {
- String url = "jdbc:h2:" + dir + "/" + dbName;
- String file = "data/test.sql";
- Script.execute(url, user, password, file);
- DeleteDbFiles.execute(dir, dbName, true);
- RunScript.execute(url, user, password, file, null, false);
-}
-</pre>
-<p>
-See also the sample application <code>org.h2.samples.Compact</code>.
-The commands <code>SCRIPT / RUNSCRIPT</code> can be used as well to create a backup
-of a database and re-build the database from the script.
-</p>
-
-<h2 id="cache_settings">Cache Settings</h2>
-<p>
-The database keeps most frequently used data in the main memory.
-The amount of memory used for caching can be changed using the setting
-<code>CACHE_SIZE</code>. This setting can be set in the database connection URL
-(<code>jdbc:h2:~/test;CACHE_SIZE=131072</code>), or it can be changed at runtime using
-<code>SET CACHE_SIZE size</code>.
-The size of the cache, as represented by <code>CACHE_SIZE</code> is measured in KB, with each KB being 1024 bytes.
-This setting has no effect for in-memory databases.
-For persistent databases, the setting is stored in the database and re-used when the database is opened
-the next time. However, when opening an existing database, the cache size is set to at most
-half the amount of memory available for the virtual machine (Runtime.getRuntime().maxMemory()),
-even if the cache size setting stored in the database is larger; however the setting stored in the database
-is kept. Setting the cache size in the database URL or explicitly using <code>SET CACHE_SIZE</code>
-overrides this value (even if larger than the physical memory).
-To get the current used maximum cache size, use the query
-<code>SELECT * FROM INFORMATION_SCHEMA.SETTINGS WHERE NAME = 'info.CACHE_MAX_SIZE'</code>
-</p><p>
-An experimental scan-resistant cache algorithm "Two Queue" (2Q) is available.
-To enable it, append <code>;CACHE_TYPE=TQ</code> to the database URL.
-The cache might not actually improve performance.
-If you plan to use it, please run your own test cases first.
-</p><p>
-Also included is an experimental second level soft reference cache.
-Rows in this cache are only garbage collected on low memory.
-By default the second level cache is disabled.
-To enable it, use the prefix <code>SOFT_</code>.
-Example: <code>jdbc:h2:~/test;CACHE_TYPE=SOFT_LRU</code>.
-The cache might not actually improve performance.
-If you plan to use it, please run your own test cases first.
-</p><p>
-To get information about page reads and writes, and the current caching algorithm in use,
-call <code>SELECT * FROM INFORMATION_SCHEMA.SETTINGS</code>. The number of pages read / written
-is listed.
-</p>
-<h2 id="external_authentication">External authentication (Experimental)</h2>
-<p>
-External authentication allows to optionally validate user credentials externally (JAAS,LDAP,custom classes).
-Is also possible to temporary assign roles to externally authenticated users. <b>This feature is experimental and subject to change</b>
-</p>
-<p>Master user cannot be externally authenticated</p>
-<p>
-To enable external authentication on a database execute statement <code>SET AUTHENTICATOR TRUE</code>. This setting in persisted on the database.
-</p>
-<p>
-To connect on a database by using external credentials client must append <code>AUTHREALM=H2</code> to the database URL. <code>H2</code>
-is the identifier of the authentication realm (see later).
-</p>
-<p>External authentication requires to send password to the server. For this reason is works only on local connection or remote over ssl</p>
-<p>
-By default external authentication is performed through JAAS login interface (configuration name is <code>h2</code>).
-To configure JAAS add argument <code>-Djava.security.auth.login.config=jaas.conf</code>
-Here an example of <a href="https://docs.oracle.com/javase/7/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">
-JAAS login configuration file</a> content:
-</p>
-<pre>
-h2 {
- com.sun.security.auth.module.LdapLoginModule REQUIRED \
- userProvider="ldap://127.0.0.1:10389" authIdentity="uid={USERNAME},ou=people,dc=example,dc=com" \
- debug=true useSSL=false ;
-};
-</pre>
-<p>
-Is it possible to specify custom authentication settings by using
-JVM argument <code>-Dh2auth.configurationFile={urlOfH2Auth.xml}</code>. Here an example of h2auth.xml file content:
-</p>
-<pre>
-<h2Auth allowUserRegistration="false" createMissingRoles="true">
-
- <!-- realm: DUMMY authenticate users named DUMMY[0-9] with a static password -->
- <realm name="DUMMY"
- validatorClass="org.h2.security.auth.impl.FixedPasswordCredentialsValidator">
- <property name="userNamePattern" value="DUMMY[0-9]" />
- <property name="password" value="mock" />
- </realm>
-
- <!-- realm LDAPEXAMPLE:perform credentials validation on LDAP -->
- <realm name="LDAPEXAMPLE"
- validatorClass="org.h2.security.auth.impl.LdapCredentialsValidator">
- <property name="bindDnPattern" value="uid=%u,ou=people,dc=example,dc=com" />
- <property name="host" value="127.0.0.1" />
- <property name="port" value="10389" />
- <property name="secure" value="false" />
- </realm>
-
- <!-- realm JAAS: perform credentials validation by using JAAS api -->
- <realm name="JAAS"
- validatorClass="org.h2.security.auth.impl.JaasCredentialsValidator">
- <property name="appName" value="H2" />
- </realm>
-
- <!--Assign to each user role @{REALM} -->
- <userToRolesMapper class="org.h2.security.auth.impl.AssignRealmNameRole"/>
-
- <!--Assign to each user role REMOTEUSER -->
- <userToRolesMapper class="org.h2.security.auth.impl.StaticRolesMapper">
- <property name="roles" value="REMOTEUSER"/>
- </userToRolesMapper>
-</h2Auth>
-</pre>
-<p>
-Custom credentials validators must implement the interface
-<code>org.h2.api.CredentialsValidator</code>
-</p>
-<p>
-Custom criteria for role assignments must implement the interface
-<code>org.h2.api.UserToRoleMapper</code>
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/fragments.html b/modules/h2/src/docsrc/html/fragments.html
deleted file mode 100644
index 3a2aa0c..0000000
--- a/modules/h2/src/docsrc/html/fragments.html
+++ /dev/null
@@ -1,130 +0,0 @@
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html><head>
- <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
- <meta name="viewport" content="width=device-width, initial-scale=1" />
- <title>Fragments</title>
-
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="highlight()" onscroll="scroll()">
-
-<table class="nav" onmousemove="return mouseMove(event)"><tr class="nav"><td class="nav" valign="top">
-<div id = "searchMenu" style="width: 180px; overflow: hidden;">
-<div class="menu" style="white-space:nowrap;">
-<img src="images/h2-logo-2.png"
- alt="H2 database logo"
- onclick="document.location='main.html'"
- width="136" height="74"/>
- <span id = "goTop" onclick="window.scrollTo(0,0)" style="color: #fff; position:fixed; font-size: 20px; cursor: pointer;">▲</span>
-</div>
-
-<form action="submit" onsubmit="return goFirst();">
-<table width="100%" class="search">
- <tr class="search">
- <td class="search" colspan="2">
-<!-- translate
-<a href="http://translate.google.com/translate?u=http%3A%2F%2Fh2database.com"
- onclick="javascript:startTranslate();return false;">Translate</a>
-<div id = "translate" style="display:none"><div id = "google_translate_element"></div></div>
-translate -->
- </td>
- </tr>
- <tr class="search">
- <td class="search" colspan="2">
- <b><label for="search">Search:</label></b>
- </td>
- </tr>
- <tr class="search">
- <td class="search" colspan="2">
- <input id = "search" name="search" type="text" size="16" maxlength="100" onkeyup="listWords(this.value, '')" /><br />
- <input type="reset" id = "clear" style="display:none;" value="Clear" onclick="listWords('', '');" />
- </td>
- </tr>
- <tr class="search" style="display:none;" >
- <td class="search" style="width: 1%; vertical-align: middle;">
- <input id = "highlight" type="checkbox" checked="checked" onclick="highlightCurrent(this.checked, search.value)" />
- </td>
- <td class="search" style="width: 99%; padding: 0px; vertical-align: middle;">
- <label for="highlight">Highlight keyword(s)</label>
- </td>
- </tr>
- <tr class="search">
- <td class="search" colspan="2">
- <table id = "result" style="border: 0px;">
- <tr style="display:none"><td></td></tr>
- </table>
- </td>
- </tr>
-</table>
-</form>
-<div class="menu">
-<b><a href="main.html">Home</a></b><br />
-<a href="download.html">Download</a><br />
-<a href="cheatSheet.html">Cheat Sheet</a><br />
-<br />
-<b>Documentation</b><br />
-<a href="quickstart.html">Quickstart</a><br />
-<a href="installation.html">Installation</a><br />
-<a href="tutorial.html">Tutorial</a><br />
-<a href="features.html">Features</a><br />
-<a href="performance.html">Performance</a><br />
-<a href="advanced.html">Advanced</a><br />
-<br />
-<b>Reference</b><br />
-<a href="commands.html">Commands</a><br />
-<a href="functions.html">Functions</a><br />
-<a href="datatypes.html">Data Types</a><br />
-<a href="grammar.html">SQL Grammar</a><br />
-<a href="systemtables.html">System Tables</a><br />
-<a href="../javadoc/index.html">Javadoc</a><br />
-<a href="../h2.pdf">PDF (1.5 MB)</a><br />
-<br />
-<b>Support</b><br />
-<a href="faq.html">FAQ</a><br />
-<a href="sourceError.html">Error Analyzer</a><br />
-<a href="https://groups.google.com/group/h2-database">Google Group (English)</a><br />
-<a href="https://groups.google.co.jp/group/h2-database-jp">Google Group (Japanese)</a><br />
-<a href="https://groups.google.com/group/h2-cn">Google Group (Chinese)</a><br />
-<br />
-<b>Appendix</b><br />
-<a href="history.html">History & Roadmap</a><br />
-<a href="license.html">License</a><br />
-<a href="build.html">Build</a><br />
-<a href="links.html">Links</a><br />
-<a href="mvstore.html">MVStore</a><br />
-<a href="architecture.html">Architecture</a><br />
-<br />
-
-</div>
-</div>
-</td>
-
-<td class="nav" style="cursor: e-resize;" onmousedown="return mouseDown(event)" onmouseup="return mouseUp(event)"> </td>
-<td class="nav"><div class="content">
-
-<!-- } -->
-
-<!-- [close] { -->
-</div></td></tr></table>
-<script type="text/javascript" src="index.js"></script>
-<script type="text/javascript" src="search.js"></script>
-<script type="text/javascript">
-function startTranslate() {
- document.getElementById('translate').style.display='';
- var script=document.createElement('script');
- script.setAttribute("type","text/javascript");
- script.setAttribute("src", "http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit");
- document.getElementsByTagName("head")[0].appendChild(script);
-}
-function googleTranslateElementInit() {
- new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
-}
-</script>
-
-<!-- } -->
-
-</body></html>
\ No newline at end of file
diff --git a/modules/h2/src/docsrc/html/frame.html b/modules/h2/src/docsrc/html/frame.html
deleted file mode 100644
index ffa95da..0000000
--- a/modules/h2/src/docsrc/html/frame.html
+++ /dev/null
@@ -1,40 +0,0 @@
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html><head>
- <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
- <meta name="viewport" content="width=device-width, initial-scale=1" />
- <title>H2 Database Engine</title>
- <link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<script type="text/javascript">
-location.href = 'main.html';
-</script>
-</head>
-<body style="margin: 20px;">
-
-<h1>H2 Database Engine</h1>
-<p>
-Welcome to H2, the free SQL database. The main feature of H2 are:
-</p>
-<ul>
-<li>It is free to use for everybody, source code is included
-</li><li>Written in Java, but also available as native executable
-</li><li>JDBC and (partial) ODBC API
-</li><li>Embedded and client/server modes
-</li><li>Clustering is supported
-</li><li>A web client is included
-</li></ul>
-
-<h2>No Javascript</h2>
-<p>
-If you are not automatically redirected to the main page, then
-Javascript is currently disabled or your browser does not support Javascript.
-Some features (for example the integrated search) require Javascript.
-</p><p>
-Please enable Javascript, or go ahead without it:
-<a href="main.html" style="font-size: 16px; font-weight: bold">H2 Database Engine</a>
-</p>
-
-</body></html>
\ No newline at end of file
diff --git a/modules/h2/src/docsrc/html/functions.html b/modules/h2/src/docsrc/html/functions.html
deleted file mode 100644
index 785fed9..0000000
--- a/modules/h2/src/docsrc/html/functions.html
+++ /dev/null
@@ -1,324 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Functions
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Functions</h1>
-<h2 id="functions_index">Index</h2>
-<h3>Aggregate Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsAggregate">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsAggregate-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsAggregate-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsAggregate-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Numeric Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsNumeric">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsNumeric-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsNumeric-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsNumeric-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>String Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsString">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsString-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsString-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsString-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Time and Date Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsTimeDate">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsTimeDate-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsTimeDate-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsTimeDate-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>System Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsSystem">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsSystem-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsSystem-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsSystem-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Window Functions</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="functionsWindow">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="functionsWindow-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsWindow-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="functionsWindow-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<!-- railroad-start -->
-<h2>Details</h2>
-<p>Click on the header to switch between railroad diagram and BNF.</p>
-<!-- railroad-end -->
-
-<h2>Aggregate Functions</h2>
-<c:forEach var="item" items="functionsAggregate">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>Numeric Functions</h2>
-<c:forEach var="item" items="functionsNumeric">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>String Functions</h2>
-<c:forEach var="item" items="functionsString">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>Time and Date Functions</h2>
-<c:forEach var="item" items="functionsTimeDate">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>System Functions</h2>
-<c:forEach var="item" items="functionsSystem">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<h2>Window Functions</h2>
-<c:forEach var="item" items="functionsWindow">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<!--[if lte IE 7]><script language="javascript">switchBnf(null);</script><![endif]-->
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/grammar.html b/modules/h2/src/docsrc/html/grammar.html
deleted file mode 100644
index 7cc2380..0000000
--- a/modules/h2/src/docsrc/html/grammar.html
+++ /dev/null
@@ -1,178 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-SQL Grammar
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>SQL Grammar</h1>
-<h2 id="grammar_index">Index</h2>
-<h3>Literals</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="literals">
- <a href="#${item.link}">${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="literals-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="literals-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="literals-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Datetime fields</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="datetimeFields">
- <a href="#${item.link}">${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="datetimeFields-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="datetimeFields-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="datetimeFields-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<h3>Other Grammar</h3>
-<!-- syntax-start
-<p class="notranslate">
-<c:forEach var="item" items="otherGrammar">
- <a href="#${item.link}" >${item.topic}</a><br />
-</c:forEach>
-</p>
-syntax-end -->
-<!-- railroad-start -->
-<table class="notranslate index">
- <tr>
- <td class="index">
- <c:forEach var="item" items="otherGrammar-0">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="otherGrammar-1">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td><td class="index">
- <c:forEach var="item" items="otherGrammar-2">
- <a href="#${item.link}" >${item.topic}</a><br />
- </c:forEach>
- </td>
- </tr>
-</table>
-<!-- railroad-end -->
-
-<!-- railroad-start -->
-<h2>Details</h2>
-<p>Click on the header to switch between railroad diagram and BNF.</p>
-<!-- railroad-end -->
-
-<h2>Literals</h2>
-<c:forEach var="item" items="literals">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">
-${item.example}</p>
-</c:forEach>
-
-<h2>Datetime fields</h2>
-<c:forEach var="item" items="datetimeFields">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">
-${item.example}</p>
-</c:forEach>
-
-<h2>Other Grammar</h2>
-<c:forEach var="item" items="otherGrammar">
-<h3 id="${item.link}" class="notranslate" onclick="switchBnf(this)">${item.topic}</h3>
-<!-- railroad-start -->
-<pre name="bnf" style="display: none">
-${item.syntax}
-</pre>
-<div name="railroad">
-${item.railroad}
-</div>
-<!-- railroad-end -->
-<!-- syntax-start
-<pre>
-${item.syntax}
-</pre>
-syntax-end -->
-<p>${item.text}</p>
-<p>Example:</p>
-<p class="notranslate">${item.example}</p>
-</c:forEach>
-
-<!--[if lte IE 7]><script language="javascript">switchBnf(null);</script><![endif]-->
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/history.html b/modules/h2/src/docsrc/html/history.html
deleted file mode 100644
index dc398f4..0000000
--- a/modules/h2/src/docsrc/html/history.html
+++ /dev/null
@@ -1,182 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-History
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>History and Roadmap</h1>
-<a href="#changelog">
- Change Log</a><br />
-<a href="#roadmap">
- Roadmap</a><br />
-<a href="#history">
- History of this Database Engine</a><br />
-<a href="#why_java">
- Why Java</a><br />
-<a href="#supporters">
- Supporters</a><br />
-
-<h2 id="changelog">Change Log</h2>
-<p>
-The up-to-date change log is available at
-<a href="http://www.h2database.com/html/changelog.html">
-http://www.h2database.com/html/changelog.html
-</a>
-</p>
-
-<h2 id="roadmap">Roadmap</h2>
-<p>
-The current roadmap is available at
-<a href="http://www.h2database.com/html/roadmap.html">
-http://www.h2database.com/html/roadmap.html
-</a>
-</p>
-
-<h2 id="history">History of this Database Engine</h2>
-<p>
-The development of H2 was started in May 2004,
-but it was first published on December 14th 2005.
-The original author of H2, Thomas Mueller, is also the original developer of Hypersonic SQL.
-In 2001, he joined PointBase Inc. where he wrote PointBase Micro, a commercial Java SQL database.
-At that point, he had to discontinue Hypersonic SQL. The HSQLDB Group was formed
-to continued to work on the Hypersonic SQL codebase.
-The name H2 stands for Hypersonic 2, however H2 does not share code with
-Hypersonic SQL or HSQLDB. H2 is built from scratch.
-</p>
-
-<h2 id="why_java">Why Java</h2>
-<p>
-The main reasons to use a Java database are:
-</p>
-<ul>
-<li>Very simple to integrate in Java applications
-</li><li>Support for many different platforms
-</li><li>More secure than native applications (no buffer overflows)
-</li><li>User defined functions (or triggers) run very fast
-</li><li>Unicode support
-</li></ul>
-<p>
-Some think Java is too slow for low level operations,
-but this is no longer true. Garbage collection for example is
-now faster than manual memory management.
-</p><p>
-Developing Java code is faster than developing C or C++ code. When using Java,
-most time can be spent on improving the algorithms instead of
-porting the code to different platforms or doing memory management.
-Features such as Unicode and network libraries are already built-in.
-In Java, writing secure code is easier because buffer overflows can not occur.
-Features such as reflection can be used for randomized testing.
-</p><p>
-Java is future proof: a lot of companies support Java. Java is now open source.
-</p><p>
-To increase the portability and ease of use, this software depends on
-very few libraries. Features that are not available in open source
-Java implementations (such as Swing) are not used, or only used for optional features.
-</p>
-
-<h2 id="supporters">Supporters</h2>
-<p>
-Many thanks for those who reported bugs, gave valuable feedback,
-spread the word, and translated this project.
-</p>
-<p>
-Also many thanks to the donors.
-To become a donor, use PayPal (at the very bottom of the main web page).
-Donators are:
-</p>
-<ul>
-<li>Martin Wildam, Austria
-</li><li><a href="http://www.tagtraum.com">tagtraum industries incorporated, USA</a>
-</li><li><a href="http://www.timewriter.com">TimeWriter, Netherlands</a>
-</li><li><a href="http://cognitect.com">Cognitect, USA</a>
-</li><li><a href="http://www.code42.com">Code 42 Software, Inc., Minneapolis</a>
-</li><li><a href="http://www.codelutin.com">Code Lutin, France</a>
-</li><li><a href="http://www.netsuxxess.de">NetSuxxess GmbH, Germany</a>
-</li><li><a href="http://pokercopilot.com">Poker Copilot, Steve McLeod, Germany</a>
-</li><li><a href="http://skycash.com">SkyCash, Poland</a>
-</li><li><a href="http://lumber-mill.co.jp">Lumber-mill, Inc., Japan</a>
-</li><li><a href="http://www.stockmarketeye.com">StockMarketEye, USA</a>
-</li><li><a href="http://www.eckenfelder.de">Eckenfelder GmbH & Co.KG, Germany</a>
-</li><li>Jun Iyama, Japan
-</li><li>Steven Branda, USA
-</li><li>Anthony Goubard, Netherlands
-</li><li>Richard Hickey, USA
-</li><li>Alessio Jacopo D'Adamo, Italy
-</li><li>Ashwin Jayaprakash, USA
-</li><li>Donald Bleyl, USA
-</li><li>Frank Berger, Germany
-</li><li>Florent Ramiere, France
-</li><li>Antonio Casqueiro, Portugal
-</li><li>Oliver Computing LLC, USA
-</li><li>Harpal Grover Consulting Inc., USA
-</li><li>Elisabetta Berlini, Italy
-</li><li>William Gilbert, USA
-</li><li>Antonio Dieguez Rojas, Chile
-</li><li><a href="http://ontologyworks.com">Ontology Works, USA</a>
-</li><li>Pete Haidinyak, USA
-</li><li>William Osmond, USA
-</li><li>Joachim Ansorg, Germany
-</li><li>Oliver Soerensen, Germany
-</li><li>Christos Vasilakis, Greece
-</li><li>Fyodor Kupolov, Denmark
-</li><li>Jakob Jenkov, Denmark
-</li><li>Stéphane Chartrand, Switzerland
-</li><li>Glenn Kidd, USA
-</li><li>Gustav Trede, Sweden
-</li><li>Joonas Pulakka, Finland
-</li><li>Bjorn Darri Sigurdsson, Iceland
-</li><li>Gray Watson, USA
-</li><li>Erik Dick, Germany
-</li><li>Pengxiang Shao, China
-</li><li>Bilingual Marketing Group, USA
-</li><li>Philippe Marschall, Switzerland
-</li><li>Knut Staring, Norway
-</li><li>Theis Borg, Denmark
-</li><li>Mark De Mendonca Duske, USA
-</li><li>Joel A. Garringer, USA
-</li><li>Olivier Chafik, France
-</li><li>Rene Schwietzke, Germany
-</li><li>Jalpesh Patadia, USA
-</li><li>Takanori Kawashima, Japan
-</li><li>Terrence JC Huang, China
-</li><li><a href="http://www.FairGo128.com">JiaDong Huang, Australia</a>
-</li><li>Laurent van Roy, Belgium
-</li><li>Qian Chen, China
-</li><li>Clinton Hyde, USA
-</li><li>Kritchai Phromros, Thailand
-</li><li>Alan Thompson, USA
-</li><li>Ladislav Jech, Czech Republic
-</li><li>Dimitrijs Fedotovs, Latvia
-</li><li>Richard Manley-Reeve, United Kingdom
-</li><li>Daniel Cyr, ThirdHalf.com, LLC, USA
-</li><li>Peter Jünger, Germany
-</li><li>Dan Keegan, USA
-</li><li>Rafel Israels, Germany
-</li><li>Fabien Todescato, France
-</li><li>Cristan Meijer, Netherlands
-</li><li>Adam McMahon, USA
-</li><li>Fábio Gomes Lisboa Gomes, Brasil
-</li><li>Lyderic Landry, England
-</li><li>Mederp, Morocco
-</li><li>Joaquim Golay, Switzerland
-</li><li>Clemens Quoss, Germany
-</li><li>Kervin Pierre, USA
-</li><li>Jake Bellotti, Australia
-</li><li>Arun Chittanoor, USA
-</li></ul>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-embedded-2.png b/modules/h2/src/docsrc/html/images/connection-mode-embedded-2.png
deleted file mode 100644
index 7da33a3..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-embedded-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-embedded.png b/modules/h2/src/docsrc/html/images/connection-mode-embedded.png
deleted file mode 100644
index ffbccfc..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-embedded.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-mixed-2.png b/modules/h2/src/docsrc/html/images/connection-mode-mixed-2.png
deleted file mode 100644
index fd4afcd..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-mixed-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-mixed.png b/modules/h2/src/docsrc/html/images/connection-mode-mixed.png
deleted file mode 100644
index a3a3970..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-mixed.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-remote-2.png b/modules/h2/src/docsrc/html/images/connection-mode-remote-2.png
deleted file mode 100644
index b45dbb8..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-remote-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/connection-mode-remote.png b/modules/h2/src/docsrc/html/images/connection-mode-remote.png
deleted file mode 100644
index 50bba17..0000000
Binary files a/modules/h2/src/docsrc/html/images/connection-mode-remote.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/console-2.png b/modules/h2/src/docsrc/html/images/console-2.png
deleted file mode 100644
index a713644..0000000
Binary files a/modules/h2/src/docsrc/html/images/console-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/console.png b/modules/h2/src/docsrc/html/images/console.png
deleted file mode 100644
index 39a7ef5..0000000
Binary files a/modules/h2/src/docsrc/html/images/console.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/db-16.png b/modules/h2/src/docsrc/html/images/db-16.png
deleted file mode 100644
index d5340e5..0000000
Binary files a/modules/h2/src/docsrc/html/images/db-16.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/db-64-t.png b/modules/h2/src/docsrc/html/images/db-64-t.png
deleted file mode 100644
index 3680773..0000000
Binary files a/modules/h2/src/docsrc/html/images/db-64-t.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/download-2.png b/modules/h2/src/docsrc/html/images/download-2.png
deleted file mode 100644
index 00e506a..0000000
Binary files a/modules/h2/src/docsrc/html/images/download-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/download.png b/modules/h2/src/docsrc/html/images/download.png
deleted file mode 100644
index 51748dc..0000000
Binary files a/modules/h2/src/docsrc/html/images/download.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/h2-logo-2.png b/modules/h2/src/docsrc/html/images/h2-logo-2.png
deleted file mode 100644
index d8025aa..0000000
Binary files a/modules/h2/src/docsrc/html/images/h2-logo-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/h2-logo.png b/modules/h2/src/docsrc/html/images/h2-logo.png
deleted file mode 100644
index 76402f0..0000000
Binary files a/modules/h2/src/docsrc/html/images/h2-logo.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/h2-logo_square.png b/modules/h2/src/docsrc/html/images/h2-logo_square.png
deleted file mode 100644
index 2714448..0000000
Binary files a/modules/h2/src/docsrc/html/images/h2-logo_square.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/icon_disconnect.gif b/modules/h2/src/docsrc/html/images/icon_disconnect.gif
deleted file mode 100644
index 2ece8d8..0000000
Binary files a/modules/h2/src/docsrc/html/images/icon_disconnect.gif and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/language_de.png b/modules/h2/src/docsrc/html/images/language_de.png
deleted file mode 100644
index 0109c35..0000000
Binary files a/modules/h2/src/docsrc/html/images/language_de.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/language_en.gif b/modules/h2/src/docsrc/html/images/language_en.gif
deleted file mode 100644
index a48f4ad..0000000
Binary files a/modules/h2/src/docsrc/html/images/language_en.gif and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/language_ja.gif b/modules/h2/src/docsrc/html/images/language_ja.gif
deleted file mode 100644
index 5e1d040..0000000
Binary files a/modules/h2/src/docsrc/html/images/language_ja.gif and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/mail-support.png b/modules/h2/src/docsrc/html/images/mail-support.png
deleted file mode 100644
index 8ff5349..0000000
Binary files a/modules/h2/src/docsrc/html/images/mail-support.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/paypal-donate.png b/modules/h2/src/docsrc/html/images/paypal-donate.png
deleted file mode 100644
index 793ef52..0000000
Binary files a/modules/h2/src/docsrc/html/images/paypal-donate.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/performance.png b/modules/h2/src/docsrc/html/images/performance.png
deleted file mode 100644
index 368fbf7..0000000
Binary files a/modules/h2/src/docsrc/html/images/performance.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-1.png b/modules/h2/src/docsrc/html/images/quickstart-1.png
deleted file mode 100644
index 276680c..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-1.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-2.png b/modules/h2/src/docsrc/html/images/quickstart-2.png
deleted file mode 100644
index ee9fd9d..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-2.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-3.png b/modules/h2/src/docsrc/html/images/quickstart-3.png
deleted file mode 100644
index fba9e42..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-3.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-4.png b/modules/h2/src/docsrc/html/images/quickstart-4.png
deleted file mode 100644
index 08a02b5be..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-4.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-5.png b/modules/h2/src/docsrc/html/images/quickstart-5.png
deleted file mode 100644
index b2f007d..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-5.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/quickstart-6.png b/modules/h2/src/docsrc/html/images/quickstart-6.png
deleted file mode 100644
index e981477..0000000
Binary files a/modules/h2/src/docsrc/html/images/quickstart-6.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/images/screenshot.png b/modules/h2/src/docsrc/html/images/screenshot.png
deleted file mode 100644
index 9d7d7e6..0000000
Binary files a/modules/h2/src/docsrc/html/images/screenshot.png and /dev/null differ
diff --git a/modules/h2/src/docsrc/html/installation.html b/modules/h2/src/docsrc/html/installation.html
deleted file mode 100644
index 65c3f82..0000000
--- a/modules/h2/src/docsrc/html/installation.html
+++ /dev/null
@@ -1,122 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-Installation
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Installation</h1>
-
-<a href="#requirements">
- Requirements</a><br />
-<a href="#supported_platforms">
- Supported Platforms</a><br />
-<a href="#installing">
- Installing the Software</a><br />
-<a href="#directory_structure">
- Directory Structure</a><br />
-
-<h2 id="requirements">Requirements</h2>
-<p>
-To run this database, the following software stack is known to work.
-Other software most likely also works, but is not tested as much.
-</p>
-
-<h3>Database Engine</h3>
-<ul><li>Windows XP or Vista, Mac OS X, or Linux
-</li><li>Oracle Java 7 or newer
-</li><li>Recommended Windows file system: NTFS (FAT32 only supports files up to 4 GB)
-</li></ul>
-
-<h3>H2 Console</h3>
-<ul><li>Mozilla Firefox
-</li></ul>
-
-<h2 id="supported_platforms">Supported Platforms</h2>
-<p>
-As this database is written in Java, it can run on many different platforms.
-It is tested with Java 7.
-Currently, the database is developed and tested on Windows 8
-and Mac OS X using Java 7, but it also works in many other operating systems
-and using other Java runtime environments.
-All major operating systems (Windows XP, Windows Vista, Windows 7, Mac OS, Ubuntu,...) are supported.
-</p>
-
-<h2 id="installing">Installing the Software</h2>
-<p>
-To install the software, run the installer or unzip it to a directory of your choice.
-</p>
-
-<h2 id="directory_structure">Directory Structure</h2>
-<p>
-After installing, you should get the following directory structure:
-</p>
-<table class="main">
- <tr>
- <th>Directory</th>
- <th>Contents</th>
- </tr>
- <tr>
- <td class="notranslate">bin</td>
- <td>JAR and batch files</td>
- </tr>
- <tr>
- <td class="notranslate">docs</td>
- <td>Documentation</td>
- </tr>
- <tr>
- <td class="notranslate">docs/html</td>
- <td>HTML pages</td>
- </tr>
- <tr>
- <td class="notranslate">docs/javadoc</td>
- <td>Javadoc files</td>
- </tr>
- <tr>
- <td class="notranslate">ext</td>
- <td>External dependencies (downloaded when building)</td>
- </tr>
- <tr>
- <td class="notranslate">service</td>
- <td>Tools to run the database as a Windows Service</td>
- </tr>
- <tr>
- <td class="notranslate">src</td>
- <td>Source files</td>
- </tr>
- <tr>
- <td class="notranslate">src/docsrc</td>
- <td>Documentation sources</td>
- </tr>
- <tr>
- <td class="notranslate">src/installer</td>
- <td>Installer, shell, and release build script</td>
- </tr>
- <tr>
- <td class="notranslate">src/main</td>
- <td>Database engine source code</td>
- </tr>
- <tr>
- <td class="notranslate">src/test</td>
- <td>Test source code</td>
- </tr>
- <tr>
- <td class="notranslate">src/tools</td>
- <td>Tools and database adapters source code</td>
- </tr>
-</table>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/license.html b/modules/h2/src/docsrc/html/license.html
deleted file mode 100644
index d928bb1..0000000
--- a/modules/h2/src/docsrc/html/license.html
+++ /dev/null
@@ -1,404 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-License
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>License</h1>
-
-<a href="#summary">
- Summary and License FAQ</a><br />
-<a href="#mpl2">
- Mozilla Public License Version 2.0</a><br />
-<a href="#eclipse_license">
- Eclipse Public License - Version 1.0</a><br />
-<a href="#eccn">
- Export Control Classification Number (ECCN)</a><br />
-
-<h2 id="summary">Summary and License FAQ</h2>
-<p>
-H2 is dual licensed and available under the MPL 2.0 (<a href="http://www.mozilla.org/MPL/2.0">Mozilla Public License Version 2.0</a>)
-or under the EPL 1.0 (<a href="http://opensource.org/licenses/eclipse-1.0.php">Eclipse Public License</a>).
-There is a license FAQ for both the MPL and the EPL.
-</p>
-<ul>
-<li>You can use H2 for free.
-</li><li>You can integrate it into your applications (including in commercial applications) and distribute it.
-</li><li>Files containing only your code are not covered by this license (it is 'commercial friendly').
-</li><li>Modifications to the H2 source code must be published.
-</li><li>You don't need to provide the source code of H2 if you did not modify anything.
-</li><li>If you distribute a binary that includes H2, you need to add a disclaimer of liability - see the example below.
-</li></ul>
-
-<p>
-However, nobody is allowed to rename H2, modify it a little, and sell it as a database engine without telling the customers it is in fact H2.
-This happened to HSQLDB: a company called 'bungisoft' copied HSQLDB, renamed it to 'RedBase', and tried to sell it,
-hiding the fact that it was in fact just HSQLDB. It seems 'bungisoft' does not exist any more, but you can use the
-<a href="http://www.archive.org">Wayback Machine</a> and visit old web pages of <code>http://www.bungisoft.com</code>.
-</p><p>
-About porting the source code to another language (for example C# or C++): converted source code (even if done manually) stays under the same
-copyright and license as the original code. The copyright of the ported source code does not (automatically) go to the person who ported the code.
-</p>
-
-<p>
-If you distribute a binary that includes H2, you need to add the license and a disclaimer of liability
-(as you should do for your own code). You should add a disclaimer for each open source library you use.
-For example, add a file <code>3rdparty_license.txt</code> in the directory where the jar files are,
-and list all open source libraries, each one with its license and disclaimer.
-For H2, a simple solution is to copy the following text below. You may also include a copy of the complete license.
-</p>
-<pre>
-This software contains unmodified binary redistributions for
-H2 database engine (http://www.h2database.com/),
-which is dual licensed and available under the MPL 2.0
-(Mozilla Public License) or under the EPL 1.0 (Eclipse Public License).
-An original copy of the license agreement can be found at:
-http://www.h2database.com/html/license.html
-</pre>
-
-<h2 id="mpl2">Mozilla Public License Version 2.0</h2>
-
-<h3>1. Definitions</h3>
-<p>1.1. "Contributor" means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.</p>
-<p>1.2. "Contributor Version" means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor's Contribution.</p>
-<p>1.3. "Contribution" means Covered Software of a particular Contributor.</p>
-<p>1.4. "Covered Software" means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof.</p>
-<p>1.5. "Incompatible With Secondary Licenses" means</p>
-<p>a. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or</p>
-<p>b. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License.</p>
-<p>1.6. "Executable Form" means any form of the work other than Source Code Form.</p>
-<p>1.7. "Larger Work" means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software.</p>
-<p>1.8. "License" means this document.</p>
-<p>1.9. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License.</p>
-<p>1.10. "Modifications" means any of the following:</p>
-<p>a. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or</p>
-<p>b. any new file in Source Code Form that contains any Covered Software.</p>
-<p>1.11. "Patent Claims" of a Contributor means any patent claim(s), including without limitation, method, process, and apparatus claims, in any patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its Contributor Version.</p>
-<p>1.12. "Secondary License" means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License, Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses.</p>
-<p>1.13. "Source Code Form" means the form of the work preferred for making modifications.</p>
-<p>1.14. "You" (or "Your") means an individual or a legal entity exercising rights under this License. For legal entities, "You" includes any entity that controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of [...]
-
-<h3>2. License Grants and Conditions</h3>
-<h4>2.1. Grants</h4>
-<p>Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:</p>
-<ol type="a">
-<li><p>under intellectual property rights (other than patent or trademark) Licensable by such Contributor to use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and</p></li>
-<li><p>under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and otherwise transfer either its Contributions or its Contributor Version.</p></li>
-</ol>
-<h4>2.2. Effective Date</h4>
-<p>The licenses granted in Section 2.1 with respect to any Contribution become effective for each Contribution on the date the Contributor first distributes such Contribution.</p>
-<h4>2.3. Limitations on Grant Scope</h4>
-<p>The licenses granted in this Section 2 are the only rights granted under this License. No additional rights or licenses will be implied from the distribution or licensing of Covered Software under this License. Notwithstanding Section 2.1(b) above, no patent license is granted by a Contributor:</p>
-<ol type="a">
-<li><p>for any code that a Contributor has removed from Covered Software; or</p></li>
-<li><p>for infringements caused by: (i) Your and any other third party's modifications of Covered Software, or (ii) the combination of its Contributions with other software (except as part of its Contributor Version); or</p></li>
-<li><p>under Patent Claims infringed by Covered Software in the absence of its Contributions.</p></li>
-</ol>
-<p>This License does not grant any rights in the trademarks, service marks, or logos of any Contributor (except as may be necessary to comply with the notice requirements in Section 3.4).</p>
-<h4>2.4. Subsequent Licenses</h4>
-<p>No Contributor makes additional grants as a result of Your choice to distribute the Covered Software under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License (if permitted under the terms of Section 3.3).</p>
-<h4>2.5. Representation</h4>
-<p>Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or it has sufficient rights to grant the rights to its Contributions conveyed by this License.</p>
-<h4>2.6. Fair Use</h4>
-<p>This License is not intended to limit any rights You have under applicable copyright doctrines of fair use, fair dealing, or other equivalents.</p>
-<h4>2.7. Conditions</h4>
-<p>Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section 2.1.</p>
-<h3>3. Responsibilities</h3>
-<h4>3.1. Distribution of Source Form</h4>
-<p>All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipients' rights in the Source Code Form.</p>
-<h4>3.2. Distribution of Executable Form</h4>
-<p>If You distribute Covered Software in Executable Form then:</p>
-<ol type="a">
-<li><p>such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and</p></li>
-<li><p>You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients' rights in the Source Code Form under this License.</p></li>
-</ol>
-<h4>3.3. Distribution of a Larger Work</h4>
-<p>You may create and distribute a Larger Work under terms of Your choice, provided that You also comply with the requirements of this License for the Covered Software. If the Larger Work is a combination of Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is not Incompatible With Secondary Licenses, this License permits You to additionally distribute such Covered Software under the terms of such Secondary License(s), so that the recipient [...]
-<h4>3.4. Notices</h4>
-<p>You may not remove or alter the substance of any license notices (including copyright notices, patent notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the Covered Software, except that You may alter any license notices to the extent required to remedy known factual inaccuracies.</p>
-<h4>3.5. Application of Additional Terms</h4>
-<p>You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity, or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any liability incurred by such Contributor as a result of warranty, s [...]
-<h3>4. Inability to Comply Due to Statute or Regulation</h3>
-<p>If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute o [...]
-<h3>5. Termination</h3>
-<p>5.1. The rights granted under this License will terminate automatically if You fail to comply with any of its terms. However, if You become compliant, then the rights granted under this License from a particular Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the non-compliance by some reasonable means prior to 60 days after You have co [...]
-<p>5.2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate.</p>
-<p>5.3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or Your distributors under this License prior to termination shall survive termination.</p>
-<h3>6. Disclaimer of Warranty</h3>
-<p>Covered Software is provided under this License on an "as is" basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any nec [...]
-<h3>7. Limitation of Liability</h3>
-<p>Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to You for any direct, indirect, special, incidental, or consequential damages of any character including, without limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such [...]
-<h3>8. Litigation</h3>
-<p>Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction, without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a party's ability to bring cross-claims or counter-claims.</p>
-<h3>9. Miscellaneous</h3>
-<p>This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor.</p>
-<h3>10. Versions of the License</h3>
-<h4>10.1. New Versions</h4>
-<p>Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the license steward has the right to modify or publish new versions of this License. Each version will be given a distinguishing version number.</p>
-<h4>10.2. Effect of New Versions</h4>
-<p>You may distribute the Covered Software under the terms of the version of the License under which You originally received the Covered Software, or under the terms of any subsequent version published by the license steward.</p>
-<h4>10.3. Modified Versions</h4>
-<p>If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward (except to note that such modified license differs from this License).</p>
-<h4>10.4. Distributing Source Code Form that is Incompatible With Secondary Licenses</h4>
-<p>If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the terms of this version of the License, the notice described in Exhibit B of this License must be attached.</p>
-<h3>Exhibit A - Source Code Form License Notice</h3>
-<pre>
-This Source Code Form is subject to the terms of the Mozilla
-Public License, v. 2.0. If a copy of the MPL was not distributed
-with this file, you can obtain one at http://mozilla.org/MPL/2.0
-</pre>
-<p>If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.</p>
-<p>You may add additional accurate notices of copyright ownership.</p>
-<h3>Exhibit B - "Incompatible With Secondary Licenses" Notice</h3>
-<pre>
-This Source Code Form is "Incompatible With Secondary Licenses",
-as defined by the Mozilla Public License, v. 2.0.
-</pre>
-
-<h2 id="eclipse_license">Eclipse Public License - Version 1.0</h2>
-<p>
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE
-PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF
-THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
-</p>
-
-<h3>1. DEFINITIONS</h3>
-<p>
-"Contribution" means:
-</p><p>
-a) in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and
-</p><p>
-b) in the case of each subsequent Contributor:
-</p><p>
-i) changes to the Program, and
-</p><p>
-ii) additions to the Program;
-</p><p>
-where such changes and/or additions to the Program originate from and are
-distributed by that particular Contributor. A Contribution 'originates' from a
-Contributor if it was added to the Program by such Contributor itself or anyone
-acting on such Contributor's behalf. Contributions do not include additions to
-the Program which: (i) are separate modules of software distributed in conjunction
-with the Program under their own license agreement, and (ii) are not derivative
-works of the Program.
-</p><p>
-"Contributor" means any person or entity that distributes the Program.
-</p><p>
-"Licensed Patents " mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when combined
-with the Program.
-</p><p>
-"Program" means the Contributions distributed in accordance with this Agreement.
-</p><p>
-"Recipient" means anyone who receives the Program under this Agreement,
-including all Contributors.
-</p>
-
-<h3>2. GRANT OF RIGHTS</h3>
-<p>
-a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient
-a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
-derivative works of, publicly display, publicly perform, distribute and sublicense the
-Contribution of such Contributor, if any, and such derivative works, in source code
-and object code form.
-</p><p>
-b) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
-Patents to make, use, sell, offer to sell, import and otherwise transfer the
-Contribution of such Contributor, if any, in source code and object code form.
-This patent license shall apply to the combination of the Contribution and the
-Program if, at the time the Contribution is added by the Contributor, such addition
-of the Contribution causes such combination to be covered by the Licensed
-Patents. The patent license shall not apply to any other combinations which
-include the Contribution. No hardware per se is licensed hereunder.
-</p><p>
-c) Recipient understands that although each Contributor grants the licenses to
-its Contributions set forth herein, no assurances are provided by any Contributor
-that the Program does not infringe the patent or other intellectual property
-rights of any other entity. Each Contributor disclaims any liability to Recipient
-for claims brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the rights and licenses
-granted hereunder, each Recipient hereby assumes sole responsibility to secure
-any other intellectual property rights needed, if any. For example, if a third party
-patent license is required to allow Recipient to distribute the Program, it is
-Recipient's responsibility to acquire that license before distributing the Program.
-</p><p>
-d) Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in this
-Agreement.
-</p>
-
-<h3>3. REQUIREMENTS</h3>
-<p>
-A Contributor may choose to distribute the Program in object code form
-under its own license agreement, provided that:
-</p><p>
-a) it complies with the terms and conditions of this Agreement; and
-</p><p>
-b) its license agreement:
-</p><p>
-i) effectively disclaims on behalf of all Contributors all warranties and conditions,
-express and implied, including warranties or conditions of title and
-non-infringement, and implied warranties or conditions of merchantability and
-fitness for a particular purpose;
-</p><p>
-ii) effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages,
-such as lost profits;
-</p><p>
-iii) states that any provisions which differ from this Agreement are offered by
-that Contributor alone and not by any other party; and
-</p><p>
-iv) states that source code for the Program is available from such Contributor,
-and informs licensees how to obtain it in a reasonable manner on or through
-a medium customarily used for software exchange.
-</p><p>
-When the Program is made available in source code form:
-</p><p>
-a) it must be made available under this Agreement; and
-</p><p>
-b) a copy of this Agreement must be included with each copy of the Program.
-</p><p>
-Contributors may not remove or alter any copyright notices contained within
-the Program.
-</p><p>
-Each Contributor must identify itself as the originator of its Contribution,
-if any, in a manner that reasonably allows subsequent Recipients to identify
-the originator of the Contribution.
-</p>
-
-<h3>4. COMMERCIAL DISTRIBUTION</h3>
-<p>
-Commercial distributors of software may accept certain responsibilities with
-respect to end users, business partners and the like. While this license is
-intended to facilitate the commercial use of the Program, the Contributor
-who includes the Program in a commercial product offering should do so
-in a manner which does not create potential liability for other Contributors.
-Therefore, if a Contributor includes the Program in a commercial product
-offering, such Contributor ("Commercial Contributor") hereby agrees to
-defend and indemnify every other Contributor ("Indemnified Contributor")
-against any losses, damages and costs (collectively "Losses") arising from
-claims, lawsuits and other legal actions brought by a third party against the
-Indemnified Contributor to the extent caused by the acts or omissions of
-such Commercial Contributor in connection with its distribution of the
-Program in a commercial product offering. The obligations in this section
-do not apply to any claims or Losses relating to any actual or alleged
-intellectual property infringement. In order to qualify, an Indemnified
-Contributor must: a) promptly notify the Commercial Contributor in writing
-of such claim, and b) allow the Commercial Contributor to control, and
-cooperate with the Commercial Contributor in, the defense and any related
-settlement negotiations. The Indemnified Contributor may participate in
-any such claim at its own expense.
-</p><p>
-For example, a Contributor might include the Program in a commercial
-product offering, Product X. That Contributor is then a Commercial
-Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance
-claims and warranties are such Commercial Contributor's responsibility
-alone. Under this section, the Commercial Contributor would have to
-defend claims against the other Contributors related to those performance
-claims and warranties, and if a court requires any other Contributor to pay
-any damages as a result, the Commercial Contributor must pay those damages.
-</p>
-
-<h3>5. NO WARRANTY</h3>
-<p>
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM
-IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR
-CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
-WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
-PURPOSE. Each Recipient is solely responsible for determining the
-appropriateness of using and distributing the Program and assumes all
-risks associated with its exercise of rights under this Agreement, including
-but not limited to the risks and costs of program errors, compliance with
-applicable laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-</p>
-
-<h3>6. DISCLAIMER OF LIABILITY</h3>
-<p>
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER
-RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
-PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
-WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY
-RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY
-OF SUCH DAMAGES.
-</p>
-
-<h3>7. GENERAL</h3>
-<p>
-If any provision of this Agreement is invalid or unenforceable under applicable
-law, it shall not affect the validity or enforceability of the remainder of the
-terms of this Agreement, and without further action by the parties hereto,
-such provision shall be reformed to the minimum extent necessary to make
-such provision valid and enforceable.
-</p><p>
-If Recipient institutes patent litigation against any entity (including a cross-claim
-or counterclaim in a lawsuit) alleging that the Program itself (excluding
-combinations of the Program with other software or hardware) infringes such
-Recipient's patent(s), then such Recipient's rights granted under Section
-2(b) shall terminate as of the date such litigation is filed.
-</p><p>
-All Recipient's rights under this Agreement shall terminate if it fails to comply
-with any of the material terms or conditions of this Agreement and does
-not cure such failure in a reasonable period of time after becoming aware
-of such noncompliance. If all Recipient's rights under this Agreement
-terminate, Recipient agrees to cease use and distribution of the Program
-as soon as reasonably practicable. However, Recipient's obligations under
-this Agreement and any licenses granted by Recipient relating to the
-Program shall continue and survive.
-</p><p>
-Everyone is permitted to copy and distribute copies of this Agreement, but
-in order to avoid inconsistency the Agreement is copyrighted and may only
-be modified in the following manner. The Agreement Steward reserves the
-right to publish new versions (including revisions) of this Agreement from
-time to time. No one other than the Agreement Steward has the right to
-modify this Agreement. The Eclipse Foundation is the initial Agreement
-Steward. The Eclipse Foundation may assign the responsibility to serve as
-the Agreement Steward to a suitable separate entity. Each new version of
-the Agreement will be given a distinguishing version number. The Program
-(including Contributions) may always be distributed subject to the version
-of the Agreement under which it was received. In addition, after a new
-version of the Agreement is published, Contributor may elect to distribute
-the Program (including its Contributions) under the new version. Except as
-expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights
-or licenses to the intellectual property of any Contributor under this
-Agreement, whether expressly, by implication, estoppel or otherwise.
-All rights in the Program not expressly granted under this Agreement are
-reserved.
-</p><p>
-This Agreement is governed by the laws of the State of New York
-and the intellectual property laws of the United States of America.
-No party to this Agreement will bring a legal action under this Agreement more
-than one year after the cause of action arose. Each party waives its rights
-to a jury trial in any resulting litigation.
-</p>
-
-<h2 id="eccn">Export Control Classification Number (ECCN)</h2>
-<p>
-As far as we know, the <a href="http://www.bis.doc.gov/licensing/exportingbasics.htm">U.S. Export Control Classification Number (ECCN)</a> for this software is <code>5D002</code>.
-However, for legal reasons, we can make no warranty that this information is correct.
-For details, see also the <a href="http://www.apache.org/licenses/exports/">Apache Software Foundation Export Classifications page</a>.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/links.html b/modules/h2/src/docsrc/html/links.html
deleted file mode 100644
index 9750456..0000000
--- a/modules/h2/src/docsrc/html/links.html
+++ /dev/null
@@ -1,708 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-H2 In Use and Links
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>Links</h1>
-<p>
-If you want to add a link, please send it to the support email address or post it to the group.
-</p>
-<a href="#quotes">
- Quotes</a><br />
-<a href="#books">
- Books</a><br />
-<a href="#extensions">
- Extensions</a><br />
-<a href="#blog">
- Blog Articles, Videos</a><br />
-<a href="#tools">
- Database Frontends / Tools</a><br />
-<a href="#projects">
- Products and Projects</a><br />
-
-<h2 id="quotes">Quotes</h2>
-<p>
-<a href="http://groups.google.com/group/h2-database/browse_thread/thread/adee024b8af85931/1edbc4a601146ec6">
-Quote</a>:
-"This is by far the easiest and fastest database that I have ever used.
-Originally the web application that I am working on is using SQL server.
-But, in less than 15 minutes I had H2 up and working with little recoding of the SQL.
-Thanks..... "
-</p>
-
-<h2 id="books">Books</h2>
-<a href="http://code.google.com/p/seaminaction/wiki/GettingStarted">
-Seam In Action</a>
-
-<h2 id="extensions">Extensions</h2>
-<a href="http://grails.org/H2+Database+Plugin">
-Grails H2 Database Plugin</a>
-<br />
-<a href="http://code.google.com/p/h2osgi">
-h2osgi: OSGi for the H2 Database</a>
-<br />
-<a href="http://code.google.com/p/h2sharp">
-H2Sharp: ADO.NET interface for the H2 database engine</a>
-<br />
-<a href="http://www.h2gis.org">
-A spatial extension of the H2 database.</a>
-
-<h2 id="blog">Blog Articles, Videos</h2>
-<a href="http://www.youtube.com/watch?v=mlWM0r3SKkg">
-Youtube: Minecraft 1.7.3 / How to install Bukkit Server with xAuth and H2</a><br />
-<a href="http://blog.zvikico.com/2009/12/analyzing-csvs-with-h2.html">
-Analyzing CSVs with H2 in under 10 minutes (2009-12-07)</a><br />
-<a href="http://sbdevel.wordpress.com/2009/06/15/efficient-sorting-and-iteration-on-large-databases">
-Efficient sorting and iteration on large databases (2009-06-15)</a><br />
-<a href="http://blog.flexive.org/2008/12/05/porting-flexive-to-the-h2-database">
-Porting Flexive to the H2 Database (2008-12-05)</a><br />
-<a href="http://blogs.sun.com/theaquarium/entry/h2_database_with_glassfish">
-H2 Database with GlassFish (2008-11-24)</a><br />
-<a href="http://zvikico.typepad.com/problog/2008/04">
-H2 Database - Performance Tracing (2008-04-30)</a><br />
-<a href="http://www.encorewiki.org/display/encore/Open+Source+Databases+Comparison">
-Open Source Databases Comparison (2007-09-11)</a><br />
-<a href="http://thecodist.com/fiche/thecodist/article/the-open-source-frameworks-i-use">
-The Codist: The Open Source Frameworks I Use (2007-07-23)</a><br />
-<a href="http://thecodist.com/fiche/thecodist/article/sql-injections-how-not-to-get-stuck">
-The Codist: SQL Injections: How Not To Get Stuck (2007-05-08)</a><br />
-<a href="http://blogs.sun.com/coldrick/entry/new_version_of_h2_database">
-David Coldrick's Weblog: New Version of H2 Database Released (2007-01-06)</a><br />
-<a href="http://thecodist.com/fiche/thecodist/article/write-your-own-database-again-an-interview-with-the-author-of-h2-thomas-mueller">
-The Codist: Write Your Own Database, Again (2006-11-13)</a><br />
-
-<h2>Project Pages</h2>
-<a href="http://www.ohloh.net/projects/3924?p=H2+Database+Engine">
-Ohloh</a><br />
-<a href="http://freshmeat.net/projects/h2">
-Freshmeat Project Page</a><br />
-<a href="http://en.wikipedia.org/wiki/H2_%28DBMS%29">
-Wikipedia</a><br />
-<a href="http://java-source.net/open-source/database-engines/h2">
-Java Source Net</a><br />
-<a href="http://packman.links2linux.org/package/h2">
-Linux Package Manager</a><br />
-
-<h2 id="tools">Database Frontends / Tools</h2>
-
-<p><a href="http://www.alvila.com/DataFlyer">
-Dataflyer</a><br />
-A tool to browse databases and export data.
-</p>
-
-<p><a href="http://www.dbsolo.com">
-DB Solo</a><br />
-SQL query tool.
-</p>
-
-<p><a href="http://www.dbvis.com">
-DbVisualizer</a><br />
-Database tool.
-</p>
-
-<p><a href="http://executequery.org">
-Execute Query</a><br />
-Database utility written in Java.
-</p>
-
-<p><a href="http://flywaydb.org">
-Flyway</a><br />
-The agile database migration framework for Java.
-</p>
-
-<p><a href="http://www.flexive.org">
-[fleXive]</a><br />
-JavaEE 5 open source framework for the development of complex and evolving (web-)applications.
-</p>
-
-<p><a href="https://github.com/arykov/jdbc-console">
-JDBC Console</a><br />
-This small webapp gives an ability to execute SQL against datasources bound in container's JNDI.
-Based on H2 Console.
-</p>
-
-<p><a href="http://henplus.sourceforge.net">
-HenPlus</a><br />
-HenPlus is a SQL shell written in Java.
-</p>
-
-<p><a href="http://github.com/maginatics/jdbclint">
-JDBC lint</a><br />
-Helps write correct and efficient code when using the JDBC API.
-</p>
-
-<p><a href="http://www.openoffice.org">
-OpenOffice</a><br />
-Base is OpenOffice.org's database application. It provides access to relational data sources.
-</p>
-
-<p><a href="http://www.razorsql.com">
-RazorSQL</a><br />
-An SQL query tool, database browser, SQL editor, and database administration tool.
-</p>
-
-<p><a href="http://sqldeveloper.solyp.com/index.html">
-SQL Developer</a><br />
-Universal Database Frontend.
-</p>
-
-<p><a href="http://sql-workbench.net">
-SQL Workbench/J</a><br />
-Free DBMS-independent SQL tool.
-</p>
-
-<p><a href="http://www.squirrelsql.org">
-SQuirreL SQL Client</a><br />
-Graphical tool to view the structure of a database, browse the data, issue SQL commands etc.
-</p>
-
-<p><a href="http://dbcopyplugin.sf.net">
-SQuirreL DB Copy Plugin</a><br />
-Tool to copy data from one database to another.
-</p>
-
-<h2 id="projects">Products and Projects</h2>
-
-<p><a href="http://www.accuprocess.com">
-AccuProcess</a><br />
-Visual business process modeling and simulation software for business users.
-</p>
-
-<p><a href="http://www.adeptiabpm.com">
-Adeptia BPM</a><br />
-A Business Process Management (BPM) suite to quickly and easily automate business processes and workflows.
-</p>
-
-<p><a href="http://www.adeptia.com">
-Adeptia Integration</a><br />
-Process-centric, services-based application integration suite.
-</p>
-
-<p><a href="http://aejaks.sf.net">
-Aejaks</a><br />
-A server-side scripting environment to build AJAX enabled web applications.
-</p>
-
-<p><a href="http://www.axiomstack.com">
-Axiom Stack</a><br />
-A web framework that let's you write dynamic web applications with Zen-like simplicity.
-</p>
-
-<p><a href="http://cayenne.apache.org">
-Apache Cayenne</a><br />
-Open source persistence framework providing object-relational mapping (ORM) and remoting services.
-</p>
-
-<p><a href="http://jackrabbit.apache.org">
-Apache Jackrabbit</a><br />
-Open source implementation of the Java Content Repository API (JCR).
-</p>
-
-<p><a href="http://incubator.apache.org/openjpa">
-Apache OpenJPA</a><br />
-Open source implementation of the Java Persistence API (JPA).
-</p>
-
-<p><a href="http://appfuse.org">
-AppFuse</a><br />
-Helps building web applications.
-</p>
-
-<p><a href="http://www.bgblitz.com">
-BGBlitz</a><br />
-The Swiss army knife of Backgammon.
-</p>
-
-<p><a href="http://wiki.bonita.ow2.org/xwiki/bin/view/Main">
-Bonita</a><br />
-Open source workflow solution for handing long-running, user-oriented processes
-providing out of the box workflow and business process management features.
-</p>
-
-<p><a href="http://bmarks-portlet.sourceforge.net">
-Bookmarks Portlet</a><br />
-JSR 168 compliant bookmarks management portlet application.
-</p>
-
-<p><a href="http://www.claros.org">
-Claros inTouch</a><br />
-Ajax communication suite with mail, addresses, notes, IM, and rss reader.
-</p>
-
-<p><a href="http://crashplan.com/business">
-CrashPlan PRO Server</a><br />
-Easy and cross platform backup solution for business and service providers.
-</p>
-
-<p><a href="http://www.datanucleus.org">
-DataNucleus</a><br />
-Java persistent objects.
-</p>
-
-<p><a href="http://dbunit.wikidot.com">
-DbUnit</a><br />
-A JUnit extension (also usable with Ant) targeted for database-driven projects.
-</p>
-
-<p><a href="http://www.diffkit.org">
-DiffKit</a><br />
-DiffKit is a tool for comparing two tables of data, field-by-field.
-DiffKit is like the Unix diff utility, but for tables instead of lines of text.
-</p>
-
-<p><a href="http://www.martincordova.com">
-Dinamica Framework</a><br />
-Ajax/J2EE framework for RAD development (mainly oriented toward hispanic markets).
-</p>
-
-<p><a href="http://dhis2.org">
-District Health Information Software 2 (DHIS)</a><br />
-The DHIS 2 is a tool for collection, validation, analysis, and presentation of aggregate statistical data,
-tailored (but not limited) to integrated health information management activities.
-</p>
-
-<p><a href="http://www.avaje.org">
-Ebean ORM Persistence Layer</a><br />
-Open source Java Object Relational Mapping tool.
-</p>
-
-<p><a href="http://wiki.eclipse.org/CDO">
-Eclipse CDO</a><br />
-The CDO (Connected Data Objects) Model Repository is a distributed shared model framework for EMF models,
-and a fast server-based O/R mapping solution.
-</p>
-
-<p><a href="http://fabric3.codehaus.org">
-Fabric3</a><br />
-Fabric3 is a project implementing a federated service network based on the Service Component Architecture specification (http://www.osoa.org).
-</p>
-
-<p><a href="http://code.google.com/p/fit4data">
-FIT4Data</a><br />
-A testing framework for data management applications built on the Java implementation of FIT.
-</p>
-
-<p><a href="http://www.fluxcorp.com">
-Flux</a><br />
-Java job scheduler, file transfer, workflow, and BPM.
-</p>
-
-<p><a href="http://geoserver.org">
-GeoServer</a><br />
-GeoServer is a Java-based software server that allows users to view and edit geospatial data. Using open standards set forth by the Open Geospatial Consortium (OGC), GeoServer allows for great flexibility in map creation and data sharing.
-</p>
-
-<p><a href="http://code.google.com/p/gbif-providertoolkit">
-GBIF Integrated Publishing Toolkit (IPT)</a><br />
-The GBIF IPT is an open source, Java based web application that connects and serves
-three types of biodiversity data: taxon primary occurrence data,
-taxon checklists and general resource metadata.
-</p>
-
-<p><a href="http://ggc.sourceforge.net">
-GNU Gluco Control</a><br />
-Helps you to manage your diabetes.
-</p>
-
-<p><a href="http://www.goldenstudios.or.id">
-Golden T Studios</a><br />
-Fun-to-play games with a simple interface.
-</p>
-
-<p><a href="http://www.gridgain.com">
-GridGain</a><br />
-GridGain is easy to use Cloud Application Platform that enables development of
-highly scalable distributed Java and Scala applications
-that auto-scale on any grid or cloud infrastructure.
-</p>
-
-<p><a href="http://www.gs.sjts.co.jp">
-Group Session</a><br />
-Open source web groupware.
-</p>
-
-<p><a href="http://ha-jdbc.sourceforge.net">
-HA-JDBC</a><br />
-High-Availability JDBC: A JDBC proxy that provides light-weight, transparent, fault tolerant clustering capability to any underlying JDBC driver.
-</p>
-
-<p><a href="http://hibernate.org">
-Hibernate</a><br />
-Relational persistence for idiomatic Java (O-R mapping tool).
-</p>
-
-<p><a href="http://www.willuhn.de/projects/hibiscus">
-Hibicius</a><br />
-Online Banking Client for the HBCI protocol.
-</p>
-
-<p><a href="http://www.believeit.ltd.uk">
-ImageMapper</a><br />
-ImageMapper frees users from having to use file browsers to view their images.
-They get fast access to images and easy cataloguing of them via a user friendly
-interface.
-</p>
-
-<p><a href="http://jamwiki.org">
-JAMWiki</a><br />
-Java-based Wiki engine.
-</p>
-
-<p><a href="http://jaspa.upv.es">
-Jaspa</a><br />
-Java Spatial. Jaspa potentially brings around 200 spatial functions.
-</p>
-
-<p><a href="http://code.google.com/p/javasimon">
-Java Simon</a><br />
-Simple Monitoring API.
-</p>
-
-<p><a href="http://www.jboss.org/jbossjbpm">
-JBoss jBPM</a><br />
-A platform for executable process languages ranging from business process management (BPM) over workflow to service orchestration.
-</p>
-
-<p><a href="http://jboss.org/jopr">
-JBoss Jopr</a><br />
-An enterprise management solution for JBoss middleware projects and other application technologies.
-</p>
-
-<p><a href="http://jgeocoder.sourceforge.net">
-JGeocoder</a><br />
-Free Java geocoder. Geocoding is the process of estimating a latitude and longitude for a given location.
-</p>
-
-<p><a href="http://www.jgrass.org">
-JGrass</a><br />
-Java Geographic Resources Analysis Support System.
-Free, multi platform, open source GIS based on the GIS framework of uDig.
-</p>
-
-<p><a href="http://jena.sourceforge.net">
-Jena</a><br />
-Java framework for building Semantic Web applications.
-</p>
-
-<p><a href="http://jmatter.org">
-JMatter</a><br />
-Framework for constructing workgroup business applications based on the Naked Objects Architectural Pattern.
-</p>
-
-<p><a href="http://www.jooq.org">
-jOOQ (Java Object Oriented Querying)</a><br />
-jOOQ is a fluent API for typesafe SQL query construction and execution
-</p>
-
-<p><a href="http://code.google.com/p/liftweb">
-Liftweb</a><br />
-A Scala-based, secure, developer friendly web framework.
-</p>
-
-<p><a href="http://liquibase.org">
-LiquiBase</a><br />
-A tool to manage database changes and refactorings.
-</p>
-
-<p><a href="http://luntbuild.javaforge.com">
-Luntbuild</a><br />
-Build automation and management tool.
-</p>
-
-<p><a href="http://code.google.com/p/localdb">
-localdb</a><br />
-A tool that locates the full file path of the folder containing the database files.
-</p>
-
-<p><a href="http://pfgrc.jcvi.org/index.php/bioinformatics/magnolia.html">
-Magnolia</a><br />
-Microarray Data Management and Export System for PFGRC
-(Pathogen Functional Genomics Resource Center) Microarrays.
-</p>
-
-<p><a href="http://www.source-code.biz/snippets/java/8.htm">
-MiniConnectionPoolManager</a><br />
-A lightweight standalone JDBC connection pool manager.
-</p>
-
-<p><a href="http://jenkov.com/mrpersister/index.html">
-Mr. Persister</a><br />
-Simple, small and fast object relational mapping.
-</p>
-
-<p><a href="http://myna.emptybrain.info">
-Myna Application Server</a><br />
-Java web app that provides dynamic web content and Java libraries access from JavaScript.
-</p>
-
-<p><a href="http://www.codewave.de/mytunesrss.php">
-MyTunesRss</a><br />
-MyTunesRSS lets you listen to your music wherever you are.
-</p>
-
-<p><a href="http://www.ncats.nih.gov/research/tools/preclinical/preclinical-research-tools.html">
-NCGC CurveFit</a><br />
-From: NIH Chemical Genomics Center, National Institutes of Health, USA.
-An open source application in the life sciences research field. This
-application handles chemical structures and biological responses of
-thousands of compounds with the potential to handle million+ compounds.
-It utilizes an embedded H2 database to enable flexible query/retrieval
-of all data including advanced chemical substructure and similarity
-searching. The application highlights an automated curve fitting and
-classification algorithm that outperforms commercial packages in the
-field. Commercial alternatives are typically small desktop software
-that handle a few dose response curves at a time. A couple of
-commercial packages that do handle several thousand curves are very
-expensive tools (>60k USD) that require manual curation of analysis
-by the user; require a license to Oracle; lack advanced
-query/retrieval; and the ability to handle chemical structures.
-</p>
-
-<p><a href="http://www.nuxeo.org">
-Nuxeo</a><br />
-Standards-based, open source platform for building ECM applications.
-</p>
-
-<p><a href="http://www.nwiresoftware.com">
-nWire</a><br />
-Eclipse plug-in which expedites Java development.
-It's main purpose is to help developers find code quicker and easily
-understand how it relates to the rest of the application, thus,
-understand the application structure.
-</p>
-
-<p><a href="http://www.ontologyworks.com">
-Ontology Works</a><br />
-This company provides semantic technologies including deductive
-information repositories (the Ontology Works Knowledge Servers),
-semantic information fusion and semantic federation of legacy
-databases, ontology-based domain modeling, and management of the
-distributed enterprise.
-</p>
-
-<p><a href="http://www.ontoprise.de">
-Ontoprise OntoBroker</a><br />
-SemanticWeb-Middleware. It supports all W3C Semantic Web recommendations:
-OWL, RDF, RDFS, SPARQL, and F-Logic.
-</p>
-
-<p><a href="http://www.openanzo.org">
-Open Anzo</a><br />
-Semantic Application Server.
-</p>
-
-<p><a href="http://www.opengroove.org">
-OpenGroove</a><br />
-OpenGroove is a groupware program that allows users to synchronize data.
-</p>
-
-<p><a href="http://code.google.com/p/opensocial-development-environment">
-OpenSocial Development Environment (OSDE)</a><br />
-Development tool for OpenSocial application.
-</p>
-
-<p><a href="http://www.orionserver.com">
-Orion</a><br />
-J2EE Application Server.
-</p>
-
-<p><a href="http://fluid-forms.com/FluidLibs">
-P5H2</a><br />
-A library for the <a href="http://www.processing.org">Processing</a> programming language and environment.
-</p>
-
-<p><a href="http://www.phase-6.de">
-Phase-6</a><br />
-A computer based learning software.
-</p>
-
-<p><a href="http://code.google.com/p/pickle4j">
-Pickle</a><br />
-Pickle is a Java library containing classes for persistence, concurrency, and logging.
-</p>
-
-<p><a href="http://www.pimansoft.com">
-Piman</a><br />
-Water treatment projects data management.
-</p>
-
-<p><a href="http://www.polepos.org">
-PolePosition</a><br />
-Open source database benchmark.
-</p>
-
-<p><a href="http://poormans.sourceforge.net/index.html">
-Poormans</a><br />
-Very basic CMS running as a SWT application and generating static html pages.
-</p>
-
-<p><a href="http://www.railo-technologies.com">
-Railo</a><br />
-Railo is an alternative engine for the Cold Fusion Markup Language, that compiles code
-programmed in CFML into Java bytecode and executes it on a servlet engine.
-</p>
-
-<p><a href="http://www.razuna.com">
-Razuna</a><br />
-Open source Digital Asset Management System with integrated Web Content Management.
-</p>
-
-<p><a href="http://www.rifers.org">
-RIFE</a><br />
-A full-stack web application framework with tools and APIs to implement most common web features.
-</p>
-
-<p><a href="http://scriptella.javaforge.com">
-Sava</a><br />
-Open-source web-based content management system.
-</p>
-
-<p><a href="http://scriptella.javaforge.com">
-Scriptella</a><br />
-ETL (Extract-Transform-Load) and script execution tool.
-</p>
-
-<p><a href="http://www.seasar.org">
-Sesar</a><br />
-Dependency Injection Container with Aspect Oriented Programming.
-</p>
-
-<p><a href="http://semmle.com">
-SemmleCode</a><br />
-Eclipse plugin to help you improve software quality.
-</p>
-
-<p><a href="http://sequalite.sourceforge.net">
-SeQuaLite</a><br />
-A free, light-weight, java data access framework.
-</p>
-
-<p><a href="http://code.google.com/p/shapelogic">
-ShapeLogic</a><br />
-Toolkit for declarative programming, image processing and computer vision.
-</p>
-
-<p><a href="http://www.shellbook.com">
-Shellbook</a><br />
-Desktop publishing application.
-</p>
-
-<p><a href="http://www.intellibo.com">
-Signsoft intelliBO</a><br />
-Persistence middleware supporting the JDO specification.
-</p>
-
-<p><a href="http://www.simpleorm.org">
-SimpleORM</a><br />
-Simple Java Object Relational Mapping.
-</p>
-
-<p><a href="http://symmetricds.codehaus.org">
-SymmetricDS</a><br />
-A web-enabled, database independent, data synchronization/replication software.
-</p>
-
-<p><a href="http://www.smartfoxserver.com">
-SmartFoxServer</a><br />
-Platform for developing multiuser applications and games with Macromedia Flash.
-</p>
-
-<p><a href="http://code.google.com/p/sbff">
-Social Bookmarks Friend Finder</a><br />
-A GUI application that allows you to find users with similar bookmarks to the user specified (for delicious.com).
-</p>
-
-<p><a href="http://www.sormula.org">
-sormula</a><br />
-Simple object relational mapping.
-</p>
-
-<p><a href="http://www.springfuse.com">
-Springfuse</a><br />
-Code generation For Spring, Spring MVC & Hibernate.
-</p>
-
-<p><a href="http://sqlorm.sourceforge.net/index.html">
-SQLOrm</a><br />
-Java Object Relation Mapping.
-</p>
-
-<p><a href="http://csv-jdbc.com">
-StelsCSV and StelsXML</a><br />
-StelsCSV is a CSV JDBC type 4 driver that allows to perform SQL queries and other JDBC operations on text files.
-StelsXML is a XML JDBC type 4 driver that allows to perform SQL queries and other JDBC operations on XML files.
-Both use H2 as the SQL engine.
-</p>
-
-<p><a href="http://www.intertec.ch/storybook">
-StorYBook</a><br />
-A summary-based tool for novelist and script writers. It helps to keep the overview over the various traces a story has.
-</p>
-
-<p><a href="http://www.streamcruncher.com">
-StreamCruncher</a><br />
-Event (stream) processing kernel.
-</p>
-
-<p><a href="http://www.suse.com/products/suse-manager">
-SUSE Manager, part of Linux Enterprise Server 11</a><br />
-The SUSE Manager
-<a href="http://www.suse.com/blogs/suse-manager-eases-the-buden-of-compliance">
-eases the burden of compliance</a> with regulatory requirements and corporate policies.
-</p>
-
-<p><a href="http://www.gabealbert.info/tunebackup">
-Tune Backup</a><br />
-Easy-to-use backup solution for your iTunes library.
-</p>
-
-<p><a href="http://www.timewriter.com">
-TimeWriter</a><br />
-TimeWriter is a very flexible program for time administration / time tracking.
-The older versions used dBase tables.
-The new version 5 is completely rewritten, now using the H2 database.
-TimeWriter is delivered in Dutch and English.
-</p>
-
-<p><a href="http://www.weblica.ch">
-weblica</a><br />
-Desktop CMS.
-</p>
-
-<p><a href="http://www.webofweb.net">
-Web of Web</a><br />
-Collaborative and realtime interactive media platform for the web.
-</p>
-
-<p><a href="http://code.google.com/p/werkzeugkasten">
-Werkzeugkasten</a><br />
-Minimum Java Toolset.
-</p>
-
-<p><a href="http://vpda.org/">
-VPDA</a><br />
-View providers driven applications is a Java based application framework
-for building applications composed from server components - view providers.
-</p>
-
-<p><a href="http://sourceforge.net/projects/volunteerbase">
-Volunteer database</a><br />
-A database front end to register volunteers, partnership and donation for a Non Profit organization.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/main.html b/modules/h2/src/docsrc/html/main.html
deleted file mode 100644
index 620b120..0000000
--- a/modules/h2/src/docsrc/html/main.html
+++ /dev/null
@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<meta name="description" content="H2 is free SQL database written in Java"/>
-<title>
-H2 Database Engine
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>H2 Database Engine</h1>
-<p>
-Welcome to H2, the free Java SQL database engine.
-</p>
-
-<p>
-<a href="quickstart.html" style="font-size: 16px; font-weight: bold">Quickstart</a>
-<br />
-Get a fast overview.
-</p>
-
-<p>
-<a href="tutorial.html" style="font-size: 16px; font-weight: bold">Tutorial</a>
-<br />
-Go through the samples.
-</p>
-
-<p>
-<a href="features.html" style="font-size: 16px; font-weight: bold">Features</a>
-<br />
-See what this database can do and how to use these features.
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
-
diff --git a/modules/h2/src/docsrc/html/mainWeb.html b/modules/h2/src/docsrc/html/mainWeb.html
deleted file mode 100644
index a563112..0000000
--- a/modules/h2/src/docsrc/html/mainWeb.html
+++ /dev/null
@@ -1,195 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<meta name="description" content="H2 is free SQL database written in Java" />
-<title>
-H2 Database Engine
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<link rel="alternate" type="application/atom+xml" title="H2 Newsfeed (Atom)" href="http://www.h2database.com/html/newsfeed-atom.xml" />
-<link rel="alternate" type="application/rss+xml" title="H2 Newsfeed (RSS)" href="http://www.h2database.com/html/newsfeed-rss.xml" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>H2 Database Engine</h1>
-<p>
-Welcome to H2, the Java SQL database. The main features of H2 are:
-</p>
-<ul>
-<li>Very fast, open source, JDBC API
-</li><li>Embedded and server modes; in-memory databases
-</li><li>Browser based Console application
-</li><li>Small footprint: around 2 MB jar file size
-</li></ul>
-
-<table style="border: 0px; width: 470px;">
- <tr><td style="border: 0px; background-color: #eee;">
- <table style="border: 0px; margin: 0px 7px 12px 7px;">
- <tr><td style="border: 0px; background-color: #eee;" colspan="2">
- <h2 style="margin-top: 1em;">Download</h2>
- Version ${version} (${versionDate})
- </td></tr>
- <tr><td style="border: 0px; background-color: #eee;">
- <a href="http://www.h2database.com/h2-setup-${versionDate}.exe"><img src="images/download-2.png" alt="Download this database" width="22" height="22"/></a>
- </td><td style="vertical-align: middle; border: 0px; background-color: #eee;">
- <a href="http://www.h2database.com/h2-setup-${versionDate}.exe">Windows Installer (5 MB)</a>
- </td></tr>
- <tr><td style="border: 0px; background-color: #eee;">
- <a href="http://www.h2database.com/h2-${versionDate}.zip"><img src="images/download-2.png" alt="Download this database" width="22" height="22"/></a>
- </td><td style="vertical-align: middle; border: 0px; background-color: #eee;">
- <a href="http://www.h2database.com/h2-${versionDate}.zip">All Platforms (zip, 8 MB)</a>
- </td></tr>
- <tr><td style="border: 0px; background-color: #eee;" colspan="2">
- <a href="download.html">All Downloads</a>
- </td></tr>
- </table>
- </td>
- <td style="border: 0px;"> </td>
- <td style="border: 0px; background-color: #eee;">
- <table style="border: 0px; margin: 0px 7px 12px 7px;">
- <tr><td style="border: 0px; background-color: #eee;">
- <h2 style="margin-top: 1em;">Support</h2>
- <p>
- <a href="https://stackoverflow.com/questions/tagged/h2">Stack Overflow (tag H2)</a><br /><br />
- <a href="https://groups.google.com/forum/#!forum/h2-database">Google Group English</a>,
- <a href="https://groups.google.com/forum/#!forum/h2-database-jp">Japanese</a><br /><br />
- For non-technical issues, use: <br />
- <script type="text/javascript">
- <!--
- var c = 'support ';
- var d = 'db';
- var e = 'at ';
- var f = '.com';
- var g = 'h2database';
- document.write(d + c + '<!-'+'- x -' + '->' + e + '<span style="display:none"> (no sp<!-'+'- -'+'->am please) </span>' + g + f);
- //-->
- </script>
- </p>
- </td></tr>
- </table>
- </td></tr>
-
-<tr><td colspan="3" style="border: 0px; padding: 5px 0px 15px 0px;">
- <h2 style="margin-top: 1em;">Features</h2>
- <table style="width: 470px;"><tr class="notranslate">
- <th></th>
- <th>H2</th>
- <th><a href="http://db.apache.org/derby">Derby</a></th>
- <th><a href="http://hsqldb.org">HSQLDB</a></th>
- <th><a href="https://www.mysql.com/">MySQL</a></th>
- <th><a href="https://www.postgresql.org/">PostgreSQL</a></th>
- </tr><tr>
- <td>Pure Java</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareN">No</td>
- </tr><tr>
- <td>Memory Mode</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareN">No</td>
- </tr><tr>
- <td>Encrypted Database</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareN">No</td>
- </tr><tr>
- <td>ODBC Driver</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareN">No</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- </tr><tr>
- <td>Fulltext Search</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareN">No</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- </tr><tr>
- <td>Multi Version Concurrency</td>
- <td class="compareY">Yes</td>
- <td class="compareN">No</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- <td class="compareY">Yes</td>
- </tr><tr>
- <td>Footprint (embedded)</td>
- <td>~2 MB</td>
- <td>~3 MB</td>
- <td>~1.5 MB</td>
- <td>—</td>
- <td>—</td>
- </tr><tr>
- <td>Footprint (client)</td>
- <td>~500 KB</td>
- <td>~600 KB</td>
- <td>~1.5 MB</td>
- <td>~1 MB</td>
- <td>~700 KB</td>
- </tr>
- </table>
-</td></tr>
-
-<tr><td colspan="3" style="border: 0px; background-color: #eee;">
- <table style="border: 0px; margin: 0px 7px 0px 7px;">
- <tr><td style="border: 0px; background-color: #eee;">
- <h2 style="margin-top: 1em;">News</h2>
- <p>
- <b>Newsfeeds:</b>
- <a href="http://www.h2database.com/html/newsfeed-atom.xml">Full text (Atom)</a>
- or <a href="http://www.h2database.com/html/newsfeed-rss.xml">Header only (RSS)</a>.
- </p><p>
- <b>Email Newsletter:</b> Subscribe to
- <a href="https://groups.google.com/forum/#!forum/h2database-news/join">
- H2 Database News (Google account required)</a>
- to get informed about new releases.
- Your email address is only used in this context.
- </p>
- </td></tr>
- </table>
-</td></tr>
-
-<tr><td colspan="3" style="border: 0px"> </td></tr>
-
-<tr><td colspan="3" style="border: 0px; background-color: #eee;">
- <table style="border: 0px; margin: 0px 7px 5px 7px;">
- <tr><td style="border: 0px; background-color: #eee;">
- <h2 style="margin-top: 1em;">Contribute</h2>
- <p>
- You can contribute to the development of H2 by sending feedback and bug
- reports, or translate the H2 Console application (for details, start the H2 Console
- and select Options / Translate).
- To donate money, click on the PayPal button below. You will be listed as a <a href="http://h2database.com/html/history.html#supporters">supporter</a>:
- </p>
- <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
- <p>
- <input type="hidden" name="cmd" value="_s-xclick"/>
- <input type="image" src="images/paypal-donate.png" width="108" height="108" name="submit" alt="PayPal icon"/>
- <input type="hidden" name="encrypted" value="-----BEGIN PKCS7-----MIIHNwYJKoZIhvcNAQcEoIIHKDCCByQCAQExggEwMIIBLAIBADCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwDQYJKoZIhvcNAQEBBQAEgYBT5YHCnqqyWDNUoD0DGudVB/0gMr1D2iOAKr/X+zR9VGBMeZsBtgmJphsbszGxXXEGxwzIVAv/ys+8TKW/uvk9UvZcDqFbCvupXmVIv3dp143N1xHsyLQGGHd8aFNraqCF7fdFoQ8GHz [...]
- </p>
- </form>
- </td></tr>
- </table>
-</td></tr>
-
-</table>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/mvstore.html b/modules/h2/src/docsrc/html/mvstore.html
deleted file mode 100644
index 660828e..0000000
--- a/modules/h2/src/docsrc/html/mvstore.html
+++ /dev/null
@@ -1,749 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!--
-Copyright 2004-2019 H2 Group. Multiple-Licensed under the MPL 2.0,
-and the EPL 1.0 (http://h2database.com/html/license.html).
-Initial Developer: H2 Group
--->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
-<meta name="viewport" content="width=device-width, initial-scale=1" />
-<title>
-MVStore
-</title>
-<link rel="stylesheet" type="text/css" href="stylesheet.css" />
-<!-- [search] { -->
-<script type="text/javascript" src="navigation.js"></script>
-</head><body onload="frameMe();">
-<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
-<!-- } -->
-
-<h1>MVStore</h1>
-<a href="#overview">
- Overview</a><br />
-<a href="#example_code">
- Example Code</a><br />
-<a href="#store_builder">
- Store Builder</a><br />
-<a href="#r_tree">
- R-Tree</a><br />
-
-<a href="#features">
- Features</a><br />
-<a href="#maps">- Maps</a><br />
-<a href="#versions">- Versions</a><br />
-<a href="#transactions">- Transactions</a><br />
-<a href="#inMemory">- In-Memory Performance and Usage</a><br />
-<a href="#dataTypes">- Pluggable Data Types</a><br />
-<a href="#blob">- BLOB Support</a><br />
-<a href="#pluggableMap">- R-Tree and Pluggable Map Implementations</a><br />
-<a href="#caching">- Concurrent Operations and Caching</a><br />
-<a href="#logStructured">- Log Structured Storage</a><br />
-<a href="#offHeap">- Off-Heap and Pluggable Storage</a><br />
-<a href="#fileSystem">- File System Abstraction, File Locking and Online Backup</a><br />
-<a href="#encryption">- Encrypted Files</a><br />
-<a href="#tools">- Tools</a><br />
-<a href="#exceptionHandling">- Exception Handling</a><br />
-<a href="#storageEngine">- Storage Engine for H2</a><br />
-
-<a href="#fileFormat">
- File Format</a><br />
-
-<a href="#differences">
- Similar Projects and Differences to Other Storage Engines</a><br />
-<a href="#current_state">
- Current State</a><br />
-<a href="#requirements">
- Requirements</a><br />
-
-<h2 id="overview">Overview</h2>
-<p>
-The MVStore is a persistent, log structured key-value store.
-It is planned to be the next storage subsystem of H2,
-but it can also be used directly within an application, without using JDBC or SQL.
-</p>
-<ul><li>MVStore stands for "multi-version store".
-</li><li>Each store contains a number of maps that can be accessed using the <code>java.util.Map</code> interface.
-</li><li>Both file-based persistence and in-memory operation are supported.
-</li><li>It is intended to be fast, simple to use, and small.
-</li><li>Concurrent read and write operations are supported.
-</li><li>Transactions are supported (including concurrent transactions and 2-phase commit).
-</li><li>The tool is very modular.
- It supports pluggable data types and serialization,
- pluggable storage (to a file, to off-heap memory),
- pluggable map implementations (B-tree, R-tree, concurrent B-tree currently),
- BLOB storage,
- and a file system abstraction to support encrypted files and zip files.
-</li></ul>
-
-<h2 id="example_code">Example Code</h2>
-<p>
-The following sample code shows how to use the tool:
-</p>
-<pre>
-import org.h2.mvstore.*;
-
-// open the store (in-memory if fileName is null)
-MVStore s = MVStore.open(fileName);
-
-// create/get the map named "data"
-MVMap<Integer, String> map = s.openMap("data");
-
-// add and read some data
-map.put(1, "Hello World");
-System.out.println(map.get(1));
-
-// close the store (this will persist changes)
-s.close();
-</pre>
-
-<h2 id="store_builder">Store Builder</h2>
-<p>
-The <code>MVStore.Builder</code> provides a fluid interface
-to build a store if configuration options are needed.
-Example usage:
-</p>
-<pre>
-MVStore s = new MVStore.Builder().
- fileName(fileName).
- encryptionKey("007".toCharArray()).
- compress().
- open();
-</pre>
-<p>
-The list of available options is:
-</p>
-<ul><li>autoCommitBufferSize: the size of the write buffer.
-</li><li>autoCommitDisabled: to disable auto-commit.
-</li><li>backgroundExceptionHandler: a handler for
- exceptions that could occur while writing in the background.
-</li><li>cacheSize: the cache size in MB.
-</li><li>compress: compress the data when storing
- using a fast algorithm (LZF).
-</li><li>compressHigh: compress the data when storing
- using a slower algorithm (Deflate).
-</li><li>encryptionKey: the key for file encryption.
-</li><li>fileName: the name of the file, for file based stores.
-</li><li>fileStore: the storage implementation to use.
-</li><li>pageSplitSize: the point where pages are split.
-</li><li>readOnly: open the file in read-only mode.
-</li></ul>
-
-<h2 id="r_tree">R-Tree</h2>
-<p>
-The <code>MVRTreeMap</code> is an R-tree implementation
-that supports fast spatial queries. It can be used as follows:
-</p>
-<pre>
-// create an in-memory store
-MVStore s = MVStore.open(null);
-
-// open an R-tree map
-MVRTreeMap<String> r = s.openMap("data",
- new MVRTreeMap.Builder<String>());
-
-// add two key-value pairs
-// the first value is the key id (to make the key unique)
-// then the min x, max x, min y, max y
-r.add(new SpatialKey(0, -3f, -2f, 2f, 3f), "left");
-r.add(new SpatialKey(1, 3f, 4f, 4f, 5f), "right");
-
-// iterate over the intersecting keys
-Iterator<SpatialKey> it =
- r.findIntersectingKeys(new SpatialKey(0, 0f, 9f, 3f, 6f));
-for (SpatialKey k; it.hasNext();) {
- k = it.next();
- System.out.println(k + ": " + r.get(k));
-}
-s.close();
-</pre>
-<p>
-The default number of dimensions is 2. To use a different number of dimensions,
-call <code>new MVRTreeMap.Builder<String>().dimensions(3)</code>.
-The minimum number of dimensions is 1, the maximum is 32.
-</p>
-
-<h2 id="features">Features</h2>
-
-<h3 id="maps">Maps</h3>
-<p>
-Each store contains a set of named maps.
-A map is sorted by key, and supports the common lookup operations,
-including access to the first and last key, iterate over some or all keys, and so on.
-</p><p>
-Also supported, and very uncommon for maps, is fast index lookup:
-the entries of the map can be efficiently accessed like a random-access list
-(get the entry at the given index), and the index of a key can be calculated efficiently.
-That also means getting the median of two keys is very fast,
-and a range of keys can be counted very quickly.
-The iterator supports fast skipping.
-This is possible because internally, each map is organized in the form of a counted B+-tree.
-</p><p>
-In database terms, a map can be used like a table, where the key of the map is the primary key of the table,
-and the value is the row. A map can also represent an index, where the key of the map is the key
-of the index, and the value of the map is the primary key of the table (for non-unique indexes,
-the key of the map must also contain the primary key).
-</p>
-
-<h3 id="versions">Versions</h3>
-<p>
-A version is a snapshot of all the data of all maps at a given point in time.
-Creating a snapshot is fast: only those pages that are changed after a snapshot are copied.
-This behavior is also called COW (copy on write).
-Old versions are readable.
-Rollback to an old version is supported.
-</p><p>
-The following sample code show how to create a store, open a map, add some data,
-and access the current and an old version:
-</p>
-<pre>
-// create/get the map named "data"
-MVMap<Integer, String> map = s.openMap("data");
-
-// add some data
-map.put(1, "Hello");
-map.put(2, "World");
-
-// get the current version, for later use
-long oldVersion = s.getCurrentVersion();
-
-// from now on, the old version is read-only
-s.commit();
-
-// more changes, in the new version
-// changes can be rolled back if required
-// changes always go into "head" (the newest version)
-map.put(1, "Hi");
-map.remove(2);
-
-// access the old data (before the commit)
-MVMap<Integer, String> oldMap =
- map.openVersion(oldVersion);
-
-// print the old version (can be done
-// concurrently with further modifications)
-// this will print "Hello" and "World":
-System.out.println(oldMap.get(1));
-System.out.println(oldMap.get(2));
-
-// print the newest version ("Hi")
-System.out.println(map.get(1));
-</pre>
-
-<h3 id="transactions">Transactions</h3>
-<p>
-To support multiple concurrent open transactions, a transaction utility is included,
-the <code>TransactionStore</code>.
-The tool supports "read committed" transaction isolation
-with savepoints, two-phase commit, and other features typically available in a database.
-There is no limit on the size of a transaction
-(the log is written to disk for large or long running transactions).
-</p><p>
-Internally, this utility stores the old versions of changed entries in a separate map, similar to a transaction log,
-except that entries of a closed transaction are removed, and the log is usually not stored for short transactions.
-For common use cases, the storage overhead of this utility is very small compared to the overhead of a regular transaction log.
-</p>
-
-<h3 id="inMemory">In-Memory Performance and Usage</h3>
-<p>
-Performance of in-memory operations is about 50% slower than
-<code>java.util.TreeMap</code>.
-</p><p>
-The memory overhead for large maps is slightly better than for the regular
-map implementations, but there is a higher overhead per map.
-For maps with less than about 25 entries, the regular map implementations need less memory.
-</p><p>
-If no file name is specified, the store operates purely in memory.
-Except for persisting data, all features are supported in this mode
-(multi-versioning, index lookup, R-tree and so on).
-If a file name is specified, all operations occur in memory (with the same
-performance characteristics) until data is persisted.
-</p><p>
-As in all map implementations, keys need to be immutable, that means
-changing the key object after an entry has been added is not allowed.
-If a file name is specified, the value may also not be changed after
-adding an entry, because it might be serialized
-(which could happen at any time when autocommit is enabled).
-</p>
-
-<h3 id="dataTypes">Pluggable Data Types</h3>
-<p>
-Serialization is pluggable. The default serialization currently supports many common data types,
-and uses Java serialization for other objects. The following classes are currently directly supported:
-<code>Boolean, Byte, Short, Character, Integer, Long, Float, Double, BigInteger, BigDecimal,
-String, UUID, Date</code> and arrays (both primitive arrays and object arrays).
-For serialized objects, the size estimate is adjusted using an exponential moving average.
-</p><p>
-Parameterized data types are supported
-(for example one could build a string data type that limits the length).
-</p><p>
-The storage engine itself does not have any length limits, so that keys, values,
-pages, and chunks can be very big (as big as fits in memory).
-Also, there is no inherent limit to the number of maps and chunks.
-Due to using a log structured storage, there is no special case handling for large keys or pages.
-</p>
-
-<h3 id="blob">BLOB Support</h3>
-<p>
-There is a mechanism that stores large binary objects by splitting them into smaller blocks.
-This allows to store objects that don't fit in memory.
-Streaming as well as random access reads on such objects are supported.
-This tool is written on top of the store, using only the map interface.
-</p>
-
-<h3 id="pluggableMap">R-Tree and Pluggable Map Implementations</h3>
-<p>
-The map implementation is pluggable.
-In addition to the default <code>MVMap</code> (multi-version map),
-there is a multi-version R-tree map implementation for spatial operations.
-</p>
-
-<h3 id="caching">Concurrent Operations and Caching</h3>
-<p>
-Concurrent reads and writes are supported.
-All such read operations can occur in parallel. Concurrent reads from the page cache,
-as well as concurrent reads from the file system are supported.
-Write operations first read the relevant pages from disk to memory
-(this can happen concurrently), and only then modify the data.
-The in-memory parts of write operations are synchronized.
-Writing changes to the file can occur concurrently to modifying the data,
-as writing operates on a snapshot.
-</p><p>
-Caching is done on the page level.
-The page cache is a concurrent LIRS cache, which should be resistant against scan operations.
-</p><p>
-For fully scalable concurrent write operations to a map (in-memory and to disk),
-the map could be split into multiple maps in different stores ('sharding').
-The plan is to add such a mechanism later when needed.
-</p>
-
-<h3 id="logStructured">Log Structured Storage</h3>
-<p>
-Internally, changes are buffered in memory, and once enough changes have accumulated,
-they are written in one continuous disk write operation.
-Compared to traditional database storage engines,
-this should improve write performance for file systems and storage systems
-that do not efficiently support small random writes, such as Btrfs, as well as SSDs.
-(According to a test, write throughput of a common SSD increases with write block size,
-until a block size of 2 MB, and then does not further increase.)
-By default, changes are automatically written when more than a number of pages are modified,
-and once every second in a background thread, even if only little data was changed.
-Changes can also be written explicitly by calling <code>commit()</code>.
-</p><p>
-When storing, all changed pages are serialized,
-optionally compressed using the LZF algorithm,
-and written sequentially to a free area of the file.
-Each such change set is called a chunk.
-All parent pages of the changed B-trees are stored in this chunk as well,
-so that each chunk also contains the root of each changed map
-(which is the entry point for reading this version of the data).
-There is no separate index: all data is stored as a list of pages.
-Per store, there is one additional map that contains the metadata (the list of
-maps, where the root page of each map is stored, and the list of chunks).
-</p><p>
-There are usually two write operations per chunk:
-one to store the chunk data (the pages), and one to update the file header (so it points to the latest chunk).
-If the chunk is appended at the end of the file, the file header is only written at the end of the chunk.
-There is no transaction log, no undo log,
-and there are no in-place updates (however, unused chunks are overwritten by default).
-</p><p>
-Old data is kept for at least 45 seconds (configurable),
-so that there are no explicit sync operations required to guarantee data consistency.
-An application can also sync explicitly when needed.
-To reuse disk space, the chunks with the lowest amount of live data are compacted
-(the live data is stored again in the next chunk).
-To improve data locality and disk space usage, the plan is to automatically defragment and compact data.
-</p><p>
-Compared to traditional storage engines (that use a transaction log, undo log, and main storage area),
-the log structured storage is simpler, more flexible, and typically needs less disk operations per change,
-as data is only written once instead of twice or 3 times, and because the B-tree pages are
-always full (they are stored next to each other) and can be easily compressed.
-But temporarily, disk space usage might actually be a bit higher than for a regular database,
-as disk space is not immediately re-used (there are no in-place updates).
-</p>
-
-<h3 id="offHeap">Off-Heap and Pluggable Storage</h3>
-<p>
-Storage is pluggable. Unless pure in-memory operation is used, the default storage is to a single file.
-</p>
-<p>
-An off-heap storage implementation is available. This storage keeps the data in the off-heap memory,
-meaning outside of the regular garbage collected heap. This allows to use very large in-memory
-stores without having to increase the JVM heap, which would increase Java garbage collection
-pauses a lot. Memory is allocated using <code>ByteBuffer.allocateDirect</code>.
-One chunk is allocated at a time (each chunk is usually a few MB large), so that
-allocation cost is low. To use the off-heap storage, call:
-</p>
-<pre>
-OffHeapStore offHeap = new OffHeapStore();
-MVStore s = new MVStore.Builder().
- fileStore(offHeap).open();
-</pre>
-
-<h3 id="fileSystem">File System Abstraction, File Locking and Online Backup</h3>
-<p>
-The file system is pluggable. The same file system abstraction is used as H2 uses.
-The file can be encrypted using a encrypting file system wrapper.
-Other file system implementations support reading from a compressed zip or jar file.
-The file system abstraction closely matches the Java 7 file system API.
-</p>
-<p>
-Each store may only be opened once within a JVM.
-When opening a store, the file is locked in exclusive mode, so that
-the file can only be changed from within one process.
-Files can be opened in read-only mode, in which case a shared lock is used.
-</p>
-<p>
-The persisted data can be backed up at any time,
-even during write operations (online backup).
-To do that, automatic disk space reuse needs to be first disabled, so that
-new data is always appended at the end of the file.
-Then, the file can be copied. The file handle is available to the application.
-It is recommended to use the utility class <code>FileChannelInputStream</code> to do this.
-For encrypted databases, both the encrypted (raw) file content,
-as well as the clear text content, can be backed up.
-</p>
-
-<h3 id="encryption">Encrypted Files</h3>
-<p>
-File encryption ensures the data can only be read with the correct password.
-Data can be encrypted as follows:
-</p>
-<pre>
-MVStore s = new MVStore.Builder().
- fileName(fileName).
- encryptionKey("007".toCharArray()).
- open();
-</pre>
-<p>
-</p><p>
-The following algorithms and settings are used:
-</p>
-<ul><li>The password char array is cleared after use,
- to reduce the risk that the password is stolen
- even if the attacker has access to the main memory.
-</li><li>The password is hashed according to the PBKDF2 standard,
- using the SHA-256 hash algorithm.
-</li><li>The length of the salt is 64 bits,
- so that an attacker can not use a pre-calculated password hash table (rainbow table).
- It is generated using a cryptographically secure random number generator.
-</li><li>To speed up opening an encrypted stores on Android,
- the number of PBKDF2 iterations is 10.
- The higher the value, the better the protection against brute-force password cracking attacks,
- but the slower is opening a file.
-</li><li>The file itself is encrypted using the standardized disk encryption mode XTS-AES.
- Only little more than one AES-128 round per block is needed.
-</li></ul>
-
-<h3 id="tools">Tools</h3>
-<p>
-There is a tool, the <code>MVStoreTool</code>, to dump the contents of a file.
-</p>
-
-<h3 id="exceptionHandling">Exception Handling</h3>
-<p>
-This tool does not throw checked exceptions.
-Instead, unchecked exceptions are thrown if needed.
-The error message always contains the version of the tool.
-The following exceptions can occur:
-</p>
-<ul><li><code>IllegalStateException</code> if a map was already closed or
- an IO exception occurred, for example if the file was locked, is already closed,
- could not be opened or closed, if reading or writing failed,
- if the file is corrupt, or if there is an internal error in the tool.
- For such exceptions, an error code is added
- so that the application can distinguish between different error cases.
-</li><li><code>IllegalArgumentException</code> if a method was called with an illegal argument.
-</li><li><code>UnsupportedOperationException</code> if a method was called that is not supported,
- for example trying to modify a read-only map.
-</li><li><code>ConcurrentModificationException</code> if a map is modified concurrently.
-</li></ul>
-
-<h3 id="storageEngine">Storage Engine for H2</h3>
-<p>
-For H2 version 1.4 and newer, the MVStore is the default storage engine
-(supporting SQL, JDBC, transactions, MVCC, and so on).
-For older versions, append
-<code>;MV_STORE=TRUE</code>
-to the database URL.
-</p>
-
-<h2 id="fileFormat">File Format</h2>
-<p>
-The data is stored in one file.
-The file contains two file headers (for safety), and a number of chunks.
-The file headers are one block each; a block is 4096 bytes.
-Each chunk is at least one block, but typically 200 blocks or more.
-Data is stored in the chunks in the form of a
-<a href="https://en.wikipedia.org/wiki/Log-structured_file_system">log structured storage</a>.
-There is one chunk for every version.
-</p>
-<pre>
-[ file header 1 ] [ file header 2 ] [ chunk ] [ chunk ] ... [ chunk ]
-</pre>
-<p>
-Each chunk contains a number of B-tree pages.
-As an example, the following code:
-</p>
-<pre>
-MVStore s = MVStore.open(fileName);
-MVMap<Integer, String> map = s.openMap("data");
-for (int i = 0; i < 400; i++) {
- map.put(i, "Hello");
-}
-s.commit();
-for (int i = 0; i < 100; i++) {
- map.put(i, "Hi");
-}
-s.commit();
-s.close();
-</pre>
-<p>
-will result in the following two chunks (excluding metadata):
-</p>
-<p>
-<b>Chunk 1:</b><br />
-- Page 1: (root) node with 2 entries pointing to page 2 and 3<br />
-- Page 2: leaf with 140 entries (keys 0 - 139)<br />
-- Page 3: leaf with 260 entries (keys 140 - 399)<br />
-</p>
-<p>
-<b>Chunk 2:</b><br />
-- Page 4: (root) node with 2 entries pointing to page 5 and 3<br />
-- Page 5: leaf with 140 entries (keys 0 - 139)<br />
-</p>
-<p>
-That means each chunk contains the changes of one version:
-the new version of the changed pages and the parent pages, recursively, up to the root page.
-Pages in subsequent chunks refer to pages in earlier chunks.
-</p>
-
-<h3>File Header</h3>
-<p>
-There are two file headers, which normally contain the exact same data.
-But once in a while, the file headers are updated, and writing could partially fail,
-which could corrupt a header. That's why there is a second header.
-Only the file headers are updated in this way (called "in-place update").
-The headers contain the following data:
-</p>
-<pre>
-H:2,block:2,blockSize:1000,chunk:7,created:1441235ef73,format:1,version:7,fletcher:3044e6cc
-</pre>
-<p>
-The data is stored in the form of a key-value pair.
-Each value is stored as a hexadecimal number. The entries are:
-</p>
-<ul><li>H: The entry "H:2" stands for the H2 database.
-</li><li>block: The block number where one of the newest chunks starts
- (but not necessarily the newest).
-</li><li>blockSize: The block size of the file; currently always hex 1000, which is decimal 4096,
- to match the <a href="https://en.wikipedia.org/wiki/Disk_sector">disk sector</a>
- length of modern hard disks.
-</li><li>chunk: The chunk id, which is normally the same value as the version;
- however, the chunk id might roll over to 0, while the version doesn't.
-</li><li>created: The number of milliseconds since 1970 when the file was created.
-</li><li>format: The file format number. Currently 1.
-</li><li>version: The version number of the chunk.
-</li><li>fletcher: The <a href="https://en.wikipedia.org/wiki/Fletcher's_checksum">
- Fletcher-32 checksum</a> of the header.
-</li></ul>
-<p>
-When opening the file, both headers are read and the checksum is verified.
-If both headers are valid, the one with the newer version is used.
-The chunk with the latest version is then detected (details about this see below),
-and the rest of the metadata is read from there.
-If the chunk id, block and version are not stored in the file header,
-then the latest chunk lookup starts with the last chunk in the file.
-</p>
-<p>
-</p>
-
-<h3>Chunk Format</h3>
-<p>
-There is one chunk per version.
-Each chunk consists of a header, the pages that were modified in this version, and a footer.
-The pages contain the actual data of the maps.
-The pages inside a chunk are stored right after the header, next to each other (unaligned).
-The size of a chunk is a multiple of the block size.
-The footer is stored in the last 128 bytes of the chunk.
-</p>
-<pre>
-[ header ] [ page ] [ page ] ... [ page ] [ footer ]
-</pre>
-<p>
-The footer allows to verify that the chunk is completely written (a chunk is written as one write operation),
-and allows to find the start position of the very last chunk in the file.
-The chunk header and footer contain the following data:
-</p>
-<pre>
-chunk:1,block:2,len:1,map:6,max:1c0,next:3,pages:2,root:4000004f8c,time:1fc,version:1
-chunk:1,block:2,version:1,fletcher:aed9a4f6
-</pre>
-<p>
-The fields of the chunk header and footer are:
-</p>
-<ul><li>chunk: The chunk id.
-</li><li>block: The first block of the chunk (multiply by the block size to get the position in the file).
-</li><li>len: The size of the chunk in number of blocks.
-</li><li>map: The id of the newest map; incremented when a new map is created.
-</li><li>max: The sum of all maximum page sizes (see page format).
-</li><li>next: The predicted start block of the next chunk.
-</li><li>pages: The number of pages in the chunk.
-</li><li>root: The position of the metadata root page (see page format).
-</li><li>time: The time the chunk was written, in milliseconds after the file was created.
-</li><li>version: The version this chunk represents.
-</li><li>fletcher: The checksum of the footer.
-</li></ul>
-<p>
-Chunks are never updated in-place. Each chunk contains the pages that were
-changed in that version (there is one chunk per version, see above),
-plus all the parent nodes of those pages, recursively, up to the root page.
-If an entry in a map is changed, removed, or added, then the respective page is copied,
-modified, and stored in the next chunk, and the number of live pages in the old chunk is decremented.
-This mechanism is called copy-on-write, and is similar to how the
-<a href="https://en.wikipedia.org/wiki/Btrfs">Btrfs</a> file system works.
-Chunks without live pages are marked as free, so the space can be re-used by more recent chunks.
-Because not all chunks are of the same size, there can be a number of free blocks in front of a chunk
-for some time (until a small chunk is written or the chunks are compacted).
-There is a <a href="http://stackoverflow.com/questions/13650134/after-how-many-seconds-are-file-system-write-buffers-typically-flushed">
-delay of 45 seconds</a> (by default) before a free chunk is overwritten,
-to ensure new versions are persisted first.
-</p>
-<p>
-How the newest chunk is located when opening a store:
-The file header contains the position of a recent chunk, but not always the newest one.
-This is to reduce the number of file header updates.
-After opening the file, the file headers, and the chunk footer of the very last chunk
-(at the end of the file) are read.
-From those candidates, the header of the most recent chunk is read.
-If it contains a "next" pointer (see above), those chunk's header and footer are read as well.
-If it turned out to be a newer valid chunk, this is repeated, until the newest chunk was found.
-Before writing a chunk, the position of the next chunk is predicted based on the assumption
-that the next chunk will be of the same size as the current one.
-When the next chunk is written, and the previous
-prediction turned out to be incorrect, the file header is updated as well.
-In any case, the file header is updated if the next chain gets longer than 20 hops.
-</p>
-
-<h3>Page Format</h3>
-<p>
-Each map is a <a href="https://en.wikipedia.org/wiki/B-tree">B-tree</a>,
-and the map data is stored in (B-tree-) pages.
-There are leaf pages that contain the key-value pairs of the map,
-and internal nodes, which only contain keys and pointers to leaf pages.
-The root of a tree is either a leaf or an internal node.
-Unlike file header and chunk header and footer, the page data is not human readable.
-Instead, it is stored as byte arrays, with long (8 bytes), int (4 bytes), short (2 bytes),
-and <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">variable size int and long</a>
-(1 to 5 / 10 bytes). The page format is:
-</p>
-<ul><li>length (int): Length of the page in bytes.
-</li><li>checksum (short): Checksum (chunk id xor offset within the chunk xor page length).
-</li><li>mapId (variable size int): The id of the map this page belongs to.
-</li><li>len (variable size int): The number of keys in the page.
-</li><li>type (byte): The page type (0 for leaf page, 1 for internal node;
- plus 2 if the keys and values are compressed with the LZF algorithm, or
- plus 6 if the keys and values are compressed with the Deflate algorithm).
-</li><li>children (array of long; internal nodes only): The position of the children.
-</li><li>childCounts (array of variable size long; internal nodes only):
- The total number of entries for the given child page.
-</li><li>keys (byte array): All keys, stored depending on the data type.
-</li><li>values (byte array; leaf pages only): All values, stored depending on the data type.
-</li></ul>
-<p>
-Even though this is not required by the file format, pages are stored in the following order:
-For each map, the root page is stored first, then the internal nodes (if there are any),
-and then the leaf pages.
-This should speed up reads for media where sequential reads are faster than random access reads.
-The metadata map is stored at the end of a chunk.
-</p>
-<p>
-Pointers to pages are stored as a long, using a special format:
-26 bits for the chunk id, 32 bits for the offset within the chunk, 5 bits for the length code,
-1 bit for the page type (leaf or internal node).
-The page type is encoded so that when clearing or removing a map, leaf pages don't
-have to be read (internal nodes do have to be read in order to know where all the pages are;
-but in a typical B-tree the vast majority of the pages are leaf pages).
-The absolute file position is not included so that chunks can be
-moved within the file without having to change page pointers;
-only the chunk metadata needs to be changed.
-The length code is a number from 0 to 31, where 0 means the maximum length
-of the page is 32 bytes, 1 means 48 bytes, 2: 64, 3: 96, 4: 128, 5: 192, and so on until 31 which
-means longer than 1 MB. That way, reading a page only requires one
-read operation (except for very large pages).
-The sum of the maximum length of all pages is stored in the chunk metadata (field "max"),
-and when a page is marked as removed, the live maximum length is adjusted.
-This allows to estimate the amount of free space within a block, in addition to the number of free pages.
-</p>
-<p>
-The total number of entries in child pages are kept to allow efficient range counting,
-lookup by index, and skip operations.
-The pages form a <a href="https://www.chiark.greenend.org.uk/~sgtatham/algorithms/cbtree.html">counted B-tree</a>.
-</p>
-<p>
-Data compression: The data after the page type are optionally compressed using the LZF algorithm.
-</p>
-
-<h3>Metadata Map</h3>
-<p>
-In addition to the user maps, there is one metadata map that contains names and
-positions of user maps, and chunk metadata.
-The very last page of a chunk contains the root page of that metadata map.
-The exact position of this root page is stored in the chunk header.
-This page (directly or indirectly) points to the root pages of all other maps.
-The metadata map of a store with a map named "data", and one chunk,
-contains the following entries:
-</p>
-<ul><li>chunk.1: The metadata of chunk 1. This is the same data as the chunk header,
- plus the number of live pages, and the maximum live length.
-</li><li>map.1: The metadata of map 1. The entries are: name, createVersion, and type.
-</li><li>name.data: The map id of the map named "data". The value is "1".
-</li><li>root.1: The root position of map 1.
-</li><li>setting.storeVersion: The store version (a user defined value).
-</li></ul>
-
-<h2 id="differences">Similar Projects and Differences to Other Storage Engines</h2>
-<p>
-Unlike similar storage engines like LevelDB and Kyoto Cabinet,
-the MVStore is written in Java
-and can easily be embedded in a Java and Android application.
-</p><p>
-The MVStore is somewhat similar to the Berkeley DB Java Edition
-because it is also written in Java,
-and is also a log structured storage, but the H2 license is more liberal.
-</p><p>
-Like SQLite 3, the MVStore keeps all data in one file.
-Unlike SQLite 3, the MVStore uses is a log structured storage.
-The plan is to make the MVStore both easier to use as well as faster than SQLite 3.
-In a recent (very simple) test, the MVStore was about twice as fast as SQLite 3 on Android.
-</p><p>
-The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek,
-and some code is shared between MVStore and MapDB.
-However, unlike MapDB, the MVStore uses is a log structured storage.
-The MVStore does not have a record size limit.
-</p>
-
-<h2 id="current_state">Current State</h2>
-<p>
-The code is still experimental at this stage.
-The API as well as the behavior may partially change.
-Features may be added and removed (even though the main features will stay).
-</p>
-
-<h2 id="requirements">Requirements</h2>
-<p>
-The MVStore is included in the latest H2 jar file.
-</p><p>
-There are no special requirements to use it.
-The MVStore should run on any JVM as well as on Android.
-</p><p>
-To build just the MVStore (without the database engine), run:
-</p>
-<pre>
-./build.sh jarMVStore
-</pre>
-<p>
-This will create the file <code>bin/h2mvstore-${version}.jar</code> (about 200 KB).
-</p>
-
-<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
diff --git a/modules/h2/src/docsrc/html/navigation.js b/modules/h2/src/docsrc/html/navigation.js
deleted file mode 100644
... 27758 lines suppressed ...