--no commit message

--no commit message

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,11 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>Issue 103: MVCC: the setting MAX_MEMORY_UNDO can currently not be supported when using
+<ul><li>New committer: Sam Van Oort has been contributing to H2 since quite some time
+    in many ways (on the mailing list, documentation, and in the form of patches).
+    He is now a committer.
+</li><li>JaQu: the order of the fields in the database no longer needs to match the order in the database.
+</li><li>Issue 103: MVCC: the setting MAX_MEMORY_UNDO can currently not be supported when using
     multi-version concurrency, that means the complete undo log must fit in memory.
 </li><li>LIKE: the escape mechanism can now be disable using ESCAPE ''.
     The default escape character can be changed using the system property h2.defaultEscape.

h2/src/docsrc/html/history.html

@@ -99,9 +99,7 @@ Many thanks for those who helped by finding and reporting bugs, gave valuable fe
 spread the word and have translated this project. Also many thanks to the donors who contributed
 via PayPal:
 </p>
-<ul>
-<li>Fyodor Kupolov, Denmark
-</li><li><a href="http://skycash.com">SkyCash, Poland</a>
+<ul><li><a href="http://skycash.com">SkyCash, Poland</a>
 </li><li>Donald Bleyl, USA
 </li><li>lumber-mill.co.jp, Japan
 </li><li>Frank Berger, Germany
@@ -119,6 +117,8 @@ via PayPal:
 </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></ul>
 
 <!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>

h2/src/docsrc/html/performance.html

@@ -25,7 +25,7 @@ Performance
 <a href="#database_profiling">
     Database Profiling</a><br />
 <a href="#database_performance_tuning">
-    Performance Tuning</a><br />
+    Database Performance Tuning</a><br />
 <a href="#fast_import">
     Fast Database Import</a><br />
 
@@ -461,6 +461,25 @@ The SQL statement ANALYZE can be used to automatically estimate the selectivity
 This command should be run from time to time to improve the query plans generated by the optimizer.
 </p>
 
+<h3>In-Memory (Hash) Indexes</h3>
+<p>
+Using in-memory indexes, specially in-memory hash indexes, can speed up
+queries and data manipulation.
+</p>
+<p>In-memory indexes are automatically used
+for in-memory databases, but can also be created for persistent databases
+using <code>CREATE MEMORY TABLE</code>. In many cases,
+the rows itself will also be kept in-memory. Please note this may cause memory
+problems for large tables.
+</p>
+<p>
+In-memory hash indexes are backed by a hash table and are usually faster than
+regular indexes. However, hash indexes only supports direct lookup (WHERE ID = ?)
+but not range scan (WHERE ID &lt; ?). To use hash indexes, use HASH as in:
+<code>CREATE UNIQUE HASH INDEX</code> and
+<code>CREATE TABLE ...(ID INT PRIMARY KEY HASH,...)</code>.
+</p>
+
 <h3>Optimization Examples</h3>
 <p>
 See <code>src/test/org/h2/samples/optimizations.sql</code> for a few examples of queries

h2/src/docsrc/html/roadmap.html

@@ -344,6 +344,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Support SCOPE_IDENTITY().
 </li><li>Support GRANT SELECT, UPDATE ON *.
 </li><li>Test Eclipse DTP.
+</li><li>Pure SQL triggers (example: update parent table if the child table is changed).
 </li><li>H2 Console: autocomplete: keep the previous setting
 </li><li>MySQL, MS SQL Server compatibility: support case sensitive (mixed case) identifiers without quotes.
 </li><li>executeBatch: option to stop at the first failed statement.

h2/src/test/org/h2/test/synth/TestBtreeIndex.java

@@ -70,6 +70,7 @@ public class TestBtreeIndex extends TestBase {
 
     private void testOne(int seed) throws SQLException {
         org.h2.Driver.load();
+        deleteDb("index");
         printTime("testIndex " + seed);
         Random random = new Random(seed);
         int distinct, prefixLength;