--no commit message

--no commit message

h2/src/docsrc/html/changelog.html

@@ -18,7 +18,10 @@ Change Log
 <h1>Change Log</h1>
 
 <h2>Next Version (unreleased)</h2>
-<ul><li>Backup: if the database contained CLOB or BLOB data, the backup
+<ul><li>The RunScript tool and SQL statement did not work with the compression method LZF.
+</li><li>Fulltext search: searching for NULL or an empty string threw an exception.
+</li><li>Lucene fulltext search: FTL_DROP_ALL did not drop the triggers.
+</li><li>Backup: if the database contained CLOB or BLOB data, the backup
     included a file entry for the LOB directory. This caused the
     restore to fail.
 </li><li>Data types: LONG is now an alias for BIGINT.

h2/src/test/org/h2/test/TestAll.java

@@ -297,6 +297,8 @@ shell tool: document encoding problem.
 mac: java -Dfile.encoding=UTF-8
 windows:
 
+download checksums (auto-verify every day)
+
 test case for running out of disk space (using a special file system)
 
 auto-build: prepare release

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

@@ -52,7 +52,7 @@ I am sorry to say that, but it looks like a corruption problem. I am very intere
 
 - Could you send the full stack trace of the exception including message text?
 - What is your database URL?
-- Do you use Tomcat or another web server? 
+- Do you use Tomcat or another web server?
     Do you unload or reload the web application?
 - You can find out if the database is corrupted when running
     SCRIPT TO 'test.sql'
@@ -60,7 +60,7 @@ I am sorry to say that, but it looks like a corruption problem. I am very intere
 - Did you use multiple connections?
 - The first workarounds is: append ;RECOVER=1 to the database URL.
     Does it work when you do this?
-- The second workarounds is: delete the index.db file (it is re-created 
+- The second workarounds is: delete the index.db file (it is re-created
     automatically) and try again. Does it work when you do this?
 - The third workarounds is: use the tool org.h2.tools.Recover to create
     the SQL script file, and then re-create the database using this script.
@@ -68,14 +68,14 @@ I am sorry to say that, but it looks like a corruption problem. I am very intere
 - With which version of H2 was this database created?
     You can find it out using:
     select * from information_schema.settings where name='CREATE_BUILD'
-- Do you use any settings or special features (for example, the setting 
+- Do you use any settings or special features (for example, the setting
     LOG=0, or two phase commit, linked tables, cache settings)?
 - Is the application multi-threaded?
 - What operating system, file system, and virtual machine
     (java -version) do you use?
 - Is it (or was it at some point) a networked file system?
 - How big is the database (file sizes)?
-- Is the database usually closed normally, or is process terminated 
+- Is the database usually closed normally, or is process terminated
     forcefully or the computer switched off?
 - Is it possible to reproduce this problem using a fresh database
     (sometimes, or always)?

h2/src/tools/org/h2/build/doc/dictionary.txt

@@ -590,4 +590,4 @@ overall httpdocs tigris eclemma separates underscore yajsw she her truncating
 relocating smtps smtp osde joist catching guesses delimiters shortlist sheet
 rowspan cheat partitioning datepart dreamsource toussi locates fred
 longnvarchar collate localdb nan bootclasspath bcp retrotranslator iterable
-ops jopr googlegroups
+ops jopr googlegroups fletcher