Documentation.

h2/src/docsrc/html/advanced.html

@@ -1065,8 +1065,9 @@ then the iteration count is not required at all.
 <p>
 The database files can be encrypted using two different algorithms: AES-128 and
 XTEA (using 32 rounds). The reasons for supporting XTEA is performance
-(XTEA is about twice as fast as AES) and to have an alternative algorithm if
-AES is suddenly broken.
+(XTEA is a bit faster as AES in some environments) and to have an alternative algorithm if AES is suddenly broken. 
+Please note that the XTEA implementation used in this database only uses 32 rounds 
+and not 64 rounds as recommended by its inventor (as of 2010, the best known attack is on 27 rounds).
 </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

h2/src/docsrc/html/features.html

@@ -316,8 +316,8 @@ encrypted using AES-128 and XTEA encryption algorithms
 </tr><tr>
 <td>Computed Columns</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>
 <td class="compareN">No</td>
 <td class="compareY">Yes *6</td>
 </tr><tr>

h2/src/docsrc/html/performance.html

@@ -262,6 +262,8 @@ and for each step a new connection is opened and then closed.
 <p>
 The PolePosition is an open source benchmark. The algorithms are all quite simple.
 It was developed / sponsored by db4o.
+This test was not run for a longer time, so please be aware that the results below
+are for older database versions (H2 version 1.1, HSQLDB 1.8, Java 1.4).
 </p>
 <table border="1" class="bar">
 <tr><th>Test Case</th><th>Unit</th><th>H2</th><th>HSQLDB</th><th>MySQL</th></tr>
@@ -583,13 +585,14 @@ System.out.println(prof.getTop(3));
 <p>
 To speed up large imports, consider using the following options temporarily:
 </p>
-<ul><li><code>SET CACHE_SIZE</code> (a large cache is faster)
+<ul><li><code>SET LOG 0</code> (disabling the transaction log)
+</li><li><code>SET CACHE_SIZE</code> (a large cache is faster)
 </li><li><code>SET LOCK_MODE 0</code> (disable locking)
 </li><li><code>SET UNDO_LOG 0</code> (disable the session undo log)
 </li></ul>
 <p>
 These options can be set in the database URL:
-<code>jdbc:h2:~/test;CACHE_SIZE=65536;LOCK_MODE=0;UNDO_LOG=0</code>.
+<code>jdbc:h2:~/test;LOG=0;CACHE_SIZE=65536;LOCK_MODE=0;UNDO_LOG=0</code>.
 Most of those options are not recommended for regular use, that means you need to reset them after use.
 </p>
 

h2/src/docsrc/html/roadmap.html

@@ -507,6 +507,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>The error "table not found" is sometimes caused by using the wrong database.
     Add "(this database is empty)" to the exception message if applicable.
 </li><li>PostgreSQL compatibility: support escape with double \\.
+</li><li>Document the TCP server "management_db". Maybe include the IP address of the client.
 </li></ul>
 
 <h2>Not Planned</h2>