--no commit message

--no commit message

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,8 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>JaQu: the plan is to support natural (pure Java) conditions such as
+<ul><li>Better support GaeVFS (Google App Engine Virtual File System).
+</li><li>JaQu: the plan is to support natural (pure Java) conditions such as
     (id == 1 && name.equals("Test")). A proof of concept decompiler is now included (it doesn't work yet).
 </li><li>Various bugfixes and improvements in the page store mechanism (still experimental).
 </li><li>PreparedStatement.setObject now converts a java.lang.Character to a string.
@@ -28,7 +29,7 @@ Change Log
 </li><li>Issue 111: Multi-version concurrency / duplicate primary key after rollback.
 </li><li>Issue 110: Multi-version concurrency / wrong exception is thrown.
 </li><li>Parser: sequenceName.NEXTVAL and CURRVAL did not respect the schema search path.
-</li><li>The following sequence could throw the exception "Row not found when trying to delete":
+</li><li>Issue 101: The following sequence could throw the exception "Row not found when trying to delete":
     start a transaction, insert many rows, delete many rows, rollback. The number of rows depends
     on the cache size.
 </li><li>The stack trace of very common exceptions is no longer written to the .trace.db file by default.

h2/src/docsrc/html/faq.html

@@ -123,6 +123,13 @@ See <a href="advanced.html#limits_limitations">Limits and Limitations</a>.
 <br /><a name="reliable"></a>
 <h3>Is it Reliable?</h3>
 <p>
+Some users have reported that after a power failure, the database can sometimes not be 
+opened because the index file is corrupt. In that case, the index file can be deleted
+(it is automatically re-created). To avoid this, append ;LOG=2 to the database URL.
+See also: <a href="grammar.html#set_log">SET LOG</a>. This problem will be solved
+using the new 'page store' mechanism (currently experimental).
+</p>
+<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 very high. Randomized stress tests
 are run regularly. But there are probably still