Documentation.

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,17 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>SimpleResultSet: updating a result set is now supported.
+<ul><li>The script created by SCRIPT DROP did not always work if multiple views
+    existed that depend on each other.
+</li><li>MathUtils.getSecureRandom could log a warning to System.err in case
+    the /dev/random is very slow, and the System.getProperties().toString()
+    returned a string larger than 64 KB. 
+</li><li>The database file locking mechanism "FS" (;FILE_LOCK=FS) 
+    did not work on Linux since version 1.3.161.
+</li><li>Sequences: the functions NEXTVAL and CURRVAL did not work as expected
+    when using quoted, mixed case sequence names.
+</li><li>The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
+</li><li>SimpleResultSet: updating a result set is now supported.
 </li><li>Database URL: extra semicolons are not supported.
 </li></ul>
 

h2/src/docsrc/html/features.html

@@ -770,14 +770,16 @@ the INIT property. Note that multiple commands may be passed to INIT, but the se
 must be escaped, as in the example below.
 </p>
 <pre>
-String url = "jdbc:h2:mem;INIT=RUNSCRIPT FROM '~/create.sql'\\;RUNSCRIPT FROM '~/populate.sql'";
+String url = "jdbc:h2:mem;INIT=runscript from '~/create.sql'\\;runscript from '~/populate.sql'";
 </pre>
 <p>
 Please note the double backslash is only required in a Java or properties file.
 In a GUI, or in an XML file, only one backslash is required:
 </p>
 <pre>
-&lt;property name="url" value="jdbc:h2:mem:test;INIT=CREATE SCHEMA IF NOT EXISTS TEST\;RUNSCRIPT FROM '~/sql/populate.sql';DB_CLOSE_DELAY=-1" /&gt;
+&lt;property name="url" value=
+"jdbc:h2:mem:test;INIT=create schema if not exists test\;runscript from '~/sql/populate.sql';DB_CLOSE_DELAY=-1"
+/&gt;
 </pre>
 
 <h2 id="ignore_unknown_settings">Ignore Unknown Settings</h2>

h2/src/docsrc/html/roadmap.html

@@ -30,11 +30,11 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Enable "h2.modifyOnWrite".
 </li><li>Enable Mode.supportOffsetFetch by default, so that "select 1 fetch first 1 row only" works.
 </li><li>The default user name should be an empty string and not "sa".
+</li><li>Deprecate Csv.getInstance() (use the public constructor instead).
 </li></ul>
 
 <h2>Priority 1</h2>
 <ul><li>Bugfixes.
-</li><li>Test if out of disk space can corrupt a database.
 </li><li>More tests with MULTI_THREADED=1 (and MULTI_THREADED with MVCC):
     Online backup (using the 'backup' statement).
 </li><li>Server side cursors.
@@ -238,6 +238,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Improve time to open large databases (see mail 'init time for distributed setup')
 </li><li>Move Maven 2 repository from hsql.sf.net to h2database.sf.net
 </li><li>Java 1.5 tool: JdbcUtils.closeSilently(s1, s2,...)
+</li><li>Optimize A=? OR B=? to UNION if the cost is lower.
 </li><li>Javadoc: document design patterns used
 </li><li>Support custom collators, for example for natural sort (for text that contains numbers).
 </li><li>Write an article about SQLInjection (h2/src/docsrc/html/images/SQLInjection.txt)
@@ -314,7 +315,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Support a data type "timestamp with timezone" using java.util.Calendar.
 </li><li>Finer granularity for SLF4J trace - See http://code.google.com/p/h2database/issues/detail?id=62
 </li><li>Add database creation date and time to the database.
-</li><li>Optimize A=? OR B=? to UNION if the cost is lower.
 </li><li>Support ASSERTION.
 </li><li>MySQL compatibility: support comparing 1='a'
 </li><li>Support PostgreSQL lock modes: http://www.postgresql.org/docs/8.3/static/explicit-locking.html
@@ -574,6 +574,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
 </li><li>Long running transactions: log session id when detected.
 </li><li>Optimization: "select id from test" should use the index on id even without "order by".
 </li><li>Issue 362: LIMIT support for UPDATE statements (MySQL compatibility).
+</li><li>Sybase SQL Anywhere compatibility: SELECT TOP ... START AT ...
 </li></ul>
 
 <h2>Not Planned</h2>