Documentation.

h2/src/docsrc/help/help.csv

@@ -565,13 +565,14 @@ CREATE TRIGGER [ IF NOT EXISTS ] newTriggerName { BEFORE | AFTER | INSTEAD OF }
 { INSERT | UPDATE | DELETE | SELECT | ROLLBACK } [,...] ON tableName [ FOR EACH ROW ]
 [ QUEUE int ] [ NOWAIT ] CALL triggeredClassName
 ","
-Creates a new trigger. The trigger class must be public. Nested and inner
-classes are not supported.  The class must be available in the classpath of the
+Creates a new trigger. The trigger class must be public. Inner classes are not supported.
+The 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).
 
 'BEFORE' triggers are called after data conversion is made, default values are set,
 null and length constraint checks have been made;
 but before other constraints have been checked.
+If there are multiple triggers, the order in which they are called is undefined.
 
 Only row based 'AFTER' trigger can be called on rollback.
 Exceptions that occur within such triggers are ignored.

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,13 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>The source code is now switched to Java 6 (JDK 1.6) by default.
+<ul><li>H2 Console: when the settings were not stored yet (for example when running for the first time),
+	the last recently used settings were not stored. A workaround was to create the file 
+	".h2.server.properties" manually in the current user home directory, with the contents:
+	webAllowOthers=false, webPort=8082, webSSL=false,
+	0=Generic H2 (Embedded)|org.h2.Driver|jdbc\:h2\:~/test|sa
+	(where a comma is a newline).
+</li><li>The source code is now switched to Java 6 (JDK 1.6) by default.
 	Java 5 (JDK 1.5) is still supported, and the jar file is still compiled for Java 5.
 </li><li>The BOM (the byte-order-mark) character 0xfeff at the beginning of the file is ignored.
     This is for compatibility with Microsoft Excel.

h2/src/docsrc/html/faq.html

@@ -167,6 +167,7 @@ Those areas are:
 </p>
 <ul>
 <li>Platforms other than Windows XP, Linux, Mac OS X, or JVMs other than Sun 1.5 or 1.6
+</li><li>The feature <code>MULTI_THREADED</code>
 </li><li>The features <code>AUTO_SERVER</code> and
     <code>AUTO_RECONNECT</code>
 </li><li>The file locking method 'Serialized'

h2/src/test/org/h2/test/todo/supportTemplates.txt

@@ -46,6 +46,33 @@ In your view, is this a defect or a feature request?
 Please provide any additional information below.
 
 -----------------
+Hi,
+
+This looks like a corrupt database. A workarounds is: use the tool org.h2.tools.Recover to create the SQL script file, and then re-create the database using this script. Does it work when you do this?
+
+As far as I see, you are using version 1.2.128. An important corruption problem was fixed in version 1.2.135 (see the change log). Known causes for corrupt databases are:
+
+- If the database was used with a version older than 1.2.135, and the process was killed while the database was closing or writing a checkpoint.
+
+- Using the transaction isolation level READ_UNCOMMITTED (LOCK_MODE 0) while at the same time using multiple connections.
+
+- Disabling database file protection using (setting FILE_LOCK to NO in the database URL).
+
+Some other areas that are not fully tested are:
+
+- Platforms other than Windows XP, Linux, Mac OS X, or JVMs other than Sun 1.5 or 1.6
+
+- The feature MULTI_THREADED
+
+- The features AUTO_SERVER and AUTO_RECONNECT
+
+- The file locking method 'Serialized'
+
+Regards,
+Thomas
+
+-----------------
+
 
 This looks like a serious problem. I have a few questions: