Documentation.

h2/src/docsrc/html/advanced.html

@@ -183,6 +183,11 @@ creating a linked table to the same database,
 and creating a linked table to another database using the server mode if the other database is open in the same server
 (use the embedded mode instead).
 </p>
+<p>
+Data types that are not supported in H2 are also not supported for linked tables,
+for example unsigned data types if the value is outside the range of the signed type.
+In such cases, the columns needs to be cast to a supported type.
+</p>
 
 <h2 id="updatable_views">Updatable Views</h2>
 <p>

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,12 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself),
+<ul><li>String.toUpperCase() was used a few places, which is problematic when using the Turkish locale.
+    The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
+</li><li>Shell tool: the built-in command "distinct" has been removed 
+    (use the SQL statements "show tables" / "show columns from tableName" instead).
+    The result set formatting has been improved.
+</li><li>MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself),
     the wrong exception was thrown.
 </li><li>IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
 </li><li>ROWNUM() did not work in combination with IN(..). The following query did not work as expected: