Documentation.

h2/src/docsrc/html/advanced.html

@@ -1334,10 +1334,10 @@ must contain NO_UPGRADE=TRUE.
 This database has the following known limitations:
 </p>
 <ul>
-<li>Database file size limits (excluding BLOB and CLOB data):
-    With the default storage mechanism, the maximum file size is currently 256 GB for the data, and 256 GB for the index.
-    With the page store (experimental): 4 TB or higher.
-</li><li>BLOB and CLOB size limit: every CLOB or BLOB can be up to 256 GB.
+<li>Database file size limit:
+    4 TB (using the default page size of 2 KB) or higher (when using a larger page size).
+    When using the feature "h2.lobInDatabase" then this limit is including CLOB and BLOB data, 
+    otherwise this limit is excluding CLOB and BLOB data, and every CLOB or BLOB can be up to 256 GB.
 </li><li>The maximum file size for FAT or FAT32 file systems is 4 GB. That means when using FAT or FAT32,
 the limit is 4 GB for the data. This is the limitation of the file system. The database does provide a
 workaround for this problem, it is to use the file name prefix <code>split:</code>. In that case files are split into

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,11 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>EXPLAIN ANALYZE with an in-memory database threw an exception. Issue 216.
+<ul><li>The table INFORMATION_SCHEMA.SETTINGS now contains all H2-specific system properties 
+    (the ones that start with "h2.") and that are explicitly set. Previously, some H2-specific settings
+    (for example h2.analyzeAuto) were missing in this list.
+</li><li>Translation: the new messages have been translated to Spanish. Thanks a lot to Dario Fassi!
+</li><li>EXPLAIN ANALYZE with an in-memory database threw an exception. Issue 216.
 </li><li>Data modifications (inserts, updates, and deletes) are now up to 5 times faster
     because converting objects to byte arrays is avoided if possible.
 </li><li>LOG=0 is now a bit faster (previously undo log entries were still written).

h2/src/docsrc/html/roadmap.html

@@ -181,6 +181,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Eliminate undo log records if stored on disk (just one pointer per block, not per record)
 </li><li>Feature matrix as in <a href="http://www.inetsoftware.de/products/jdbc/mssql/features/default.asp">i-net software</a>.
 </li><li>Updatable result set on table without primary key or unique index.
+</li><li>Compatibility with Derby and PostgreSQL: VALUES(1), (2); SELECT * FROM (VALUES (1), (2)) AS myTable(c1). Issue 221.
 </li><li>Use LinkedList instead of ArrayList where applicable.
 </li><li>Allow execution time prepare for SELECT * FROM CSVREAD(?, 'columnNameString')
 </li><li>Support data type INTERVAL
@@ -202,7 +203,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Support linked tables to the current database
 </li><li>Support dynamic linked schema (automatically adding/updating/removing tables)
 </li><li>Clustering: adding a node should be very fast and without interrupting clients (very short lock)
-</li><li>Compatibility with Derby: VALUES(1), (2); SELECT * FROM (VALUES (1), (2)) AS myTable(c1)
 </li><li>Compatibility: # is the start of a single line comment (MySQL) but date quote (Access). Mode specific
 </li><li>Run benchmarks with JDK 1.5, JDK 1.6, java -server
 </li><li>Optimizations: faster hash function for strings, byte arrays
@@ -513,6 +513,8 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Support large GROUP BY operations. Issue 216.
 </li><li>Common Table Expression (CTE): support non-recursive queries. Issue 217.
 </li><li>Common Table Expression (CTE): avoid endless loop. Issue 218.
+</li><li>Common Table Expression (CTE): support multiple named queries. Issue 220.
+</li><li>Common Table Expression (CTE): identifier scope may be incorrect. Issue 222.
 </li></ul>
 
 <h2>Not Planned</h2>

h2/src/docsrc/html/tutorial.html

@@ -1083,6 +1083,7 @@ org.h2.fulltext.FullText.searchData(conn, text, limit, offset);
 <h3>Using the Lucene Fulltext Search</h3>
 <p>
 To use the Lucene full text search, you need the Lucene library in the classpath.
+Currently only Apache Lucene version 2.x is supported.
 How to do that depends on the application; if you use the H2 Console, you can add the Lucene
 jar file to the environment variables <code>H2DRIVERS</code> or
 <code>CLASSPATH</code>.