Documentation.

h2/src/docsrc/help/help.csv

@@ -1255,9 +1255,10 @@ SET MAX_LENGTH_INPLACE_LOB 128
 "Commands (Other)","SET MAX_LOG_SIZE","
 SET MAX_LOG_SIZE int
 ","
-Sets the maximum size of the transaction log, in megabytes. If the log exceeds the
-limit, a new stream is created. Old streams (that are not used for recovery) are
-freed automatically. The default max size is 16 MB.
+Sets the maximum size of the transaction log, in megabytes.
+If the log is larger, and if there is no open transaction, the transaction log is truncated.
+If there is an option transaction, the transaction log will continue to grow however.
+The default max size is 16 MB.
 This setting has no effect for in-memory databases.
 
 Admin rights are required to execute this command, as it affects all connections.

h2/src/docsrc/html/changelog.html

@@ -18,11 +18,21 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>DatabaseEventListener now calls setProgress whenever a statement starts and ends.
+<ul><li>Server mode: the number of CLOB / BLOB values that were cached on the server
+    is now 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default).
+</li><li>In the trace file, the query execution time was incorrect in some cases, specially
+    for the statement SET TRACE_LEVEL_FILE 2.
+</li><li>The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work
+    correctly (specially with regards to multithreading) and has been removed.
+    The message "Transaction log could not be truncated" is still written to the .trace.db file
+    if required.
+</li><li>Then reading from a resource using the prefix "classpath:", the ContextClassLoader
+    is now used if the resource can't be read otherwise.
+</li><li>DatabaseEventListener now calls setProgress whenever a statement starts and ends.
 </li><li>The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
 </li><li>Issue 378: when using views, the wrong values were bound to a parameter in some cases.
 </li><li>Terrence Huang has translated the error messages to Chinese. Thanks a lot!
-</li><li>TRUNC was added as an alias for TRUNCATE
+</li><li>TRUNC was added as an alias for TRUNCATE.
 </li></ul>
 
 <h2>Version 1.3.166 (2012-04-08)</h2>

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

@@ -56,13 +56,13 @@ Important corruption problems were fixed in version 1.2.135 and version 1.2.140
 
 I am very interested in analyzing and solving this problem. Corruption problems have top priority for me. I have a few questions:
 
+- What is your database URL?
+- Did you use LOG=0 or LOG=1? Did you read the FAQ about it?
 - Did the system ever run out of disk space?
 - Could you send the full stack trace of the exception including message text?
 - Did you use SHUTDOWN DEFRAG or the database setting DEFRAG_ALWAYS with H2 version 1.3.159 or older?
-- What is your database URL?
 - How many connections does your application use concurrently?
 - Do you use temporary tables?
-- Did you use LOG=0 or LOG=1?
 - With which version of H2 was this database created?
     You can find it out using:
     select * from information_schema.settings where name='CREATE_BUILD'