Prepare release.

e25a1675 · Thomas Mueller · 1a02949e · e25a1675 · e25a1675 · e25a1675
--- a/h2/src/docsrc/html/changelog.html
+++ b/h2/src/docsrc/html/changelog.html
@@ -18,6 +18,10 @@ Change Log
 <h1>Change Log</h1>

 <h2>Next Version (unreleased)</h2>
+<ul><li>-
+</li></ul>
+
+<h2>Version 1.3.157 (2011-06-25)</h2>
 <ul><li>The syntax for CREATE TABLE ... AS SELECT ... has been changed:
    options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise
    they might be interpreted as a part of the query.

--- a/h2/src/docsrc/text/_docs_en.utf8.txt
+++ b/h2/src/docsrc/text/_docs_en.utf8.txt
@@ -1631,7 +1631,7 @@ Non-admin users could not open a database using a mode (MODE=xxx) if the databas
 The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...". 

 @changelog_1009_li
-There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. There is a new system property "h2.storeLocalTime" that takes daylight time saving into account when storing and reading, however database files that are created or modified with this flag set can not be opened with older versions of H2. The new storage format is already supported for reading however, so that this version is forward compatible. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 
+There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 

 @changelog_1010_h2
 Version 1.3.156 (2011-06-17)

--- a/h2/src/docsrc/text/_docs_ja.utf8.txt
+++ b/h2/src/docsrc/text/_docs_ja.utf8.txt
@@ -1208,31 +1208,31 @@ SSL/TLS 接続
 AES-128

 @advanced_1403_td
-#A block encryption algorithm. See also: <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">Wikipedia: AES</a> #Birthday Paradox
+#A block encryption algorithm. See also: <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">Wikipedia: AES</a>

 @advanced_1404_td
 Birthday Paradox

 @advanced_1405_td
-#Describes the higher than expected probability that two persons in a room have the same birthday. Also valid for randomly generated UUIDs. See also: <a href="http://en.wikipedia.org/wiki/Birthday_paradox">Wikipedia: Birthday Paradox</a> #Digest
+#Describes the higher than expected probability that two persons in a room have the same birthday. Also valid for randomly generated UUIDs. See also: <a href="http://en.wikipedia.org/wiki/Birthday_paradox">Wikipedia: Birthday Paradox</a>

 @advanced_1406_td
 Digest

 @advanced_1407_td
-#Protocol to protect a password (but not to protect data). See also: <a href="http://www.faqs.org/rfcs/rfc2617.html">RFC 2617: HTTP Digest Access Authentication</a> #GCJ
+#Protocol to protect a password (but not to protect data). See also: <a href="http://www.faqs.org/rfcs/rfc2617.html">RFC 2617: HTTP Digest Access Authentication</a>

 @advanced_1408_td
 GCJ

 @advanced_1409_td
-#Compiler for Java. <a href="http://gcc.gnu.org/java">GNU Compiler for the Java</a> and <a href="http://www.dobysoft.com/products/nativej">NativeJ (commercial)</a> #HTTPS
+#Compiler for Java. <a href="http://gcc.gnu.org/java">GNU Compiler for the Java</a> and <a href="http://www.dobysoft.com/products/nativej">NativeJ (commercial)</a>

 @advanced_1410_td
 HTTPS

 @advanced_1411_td
-#A protocol to provide security to HTTP connections. See also: <a href="http://www.ietf.org/rfc/rfc2818.txt">RFC 2818: HTTP Over TLS</a> #Modes of Operation
+#A protocol to provide security to HTTP connections. See also: <a href="http://www.ietf.org/rfc/rfc2818.txt">RFC 2818: HTTP Over TLS</a>

 @advanced_1412_td
 Modes of Operation
@@ -1244,31 +1244,31 @@ Modes of Operation
 Salt

 @advanced_1415_td
-#Random number to increase the security of passwords. See also: <a href="http://en.wikipedia.org/wiki/Key_derivation_function">Wikipedia: Key derivation function</a> #SHA-256
+#Random number to increase the security of passwords. See also: <a href="http://en.wikipedia.org/wiki/Key_derivation_function">Wikipedia: Key derivation function</a>

 @advanced_1416_td
 SHA-256

 @advanced_1417_td
-#A cryptographic one-way hash function. See also: <a href="http://en.wikipedia.org/wiki/SHA_family">Wikipedia: SHA hash functions</a> #SQLインジェクション
+#A cryptographic one-way hash function. See also: <a href="http://en.wikipedia.org/wiki/SHA_family">Wikipedia: SHA hash functions</a>

 @advanced_1418_td
 SQLインジェクション

 @advanced_1419_td
-#A security vulnerability where an application embeds SQL statements or expressions in user input. See also: <a href="http://en.wikipedia.org/wiki/SQL_injection">Wikipedia: SQL Injection</a> #Watermark Attack (透かし攻撃)
+#A security vulnerability where an application embeds SQL statements or expressions in user input. See also: <a href="http://en.wikipedia.org/wiki/SQL_injection">Wikipedia: SQL Injection</a>

 @advanced_1420_td
 Watermark Attack (透かし攻撃)

 @advanced_1421_td
-#Security problem of certain encryption programs where the existence of certain data can be proven without decrypting. For more information, search in the internet for 'watermark attack cryptoloop' #SSL/TLS
+#Security problem of certain encryption programs where the existence of certain data can be proven without decrypting. For more information, search in the internet for 'watermark attack cryptoloop'

 @advanced_1422_td
 SSL/TLS

 @advanced_1423_td
-#Secure Sockets Layer / Transport Layer Security. See also: <a href="http://java.sun.com/products/jsse/">Java Secure Socket Extension (JSSE)</a> #XTEA
+#Secure Sockets Layer / Transport Layer Security. See also: <a href="http://java.sun.com/products/jsse/">Java Secure Socket Extension (JSSE)</a>

 @advanced_1424_td
 XTEA
@@ -1631,7 +1631,7 @@ Centralリポジトリの利用
 #The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...". 

 @changelog_1009_li
-#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. There is a new system property "h2.storeLocalTime" that takes daylight time saving into account when storing and reading, however database files that are created or modified with this flag set can not be opened with older versions of H2. The new storage format is already supported for reading however, so that this version is forward compatible. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 
+#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 

 @changelog_1010_h2
 #Version 1.3.156 (2011-06-17)

--- a/h2/src/docsrc/textbase/_docs_en.properties
+++ b/h2/src/docsrc/textbase/_docs_en.properties
@@ -542,7 +542,7 @@ changelog_1005_li=The optimization for COUNT(..) on columns that are not nullabl
 changelog_1006_li=PgServer\: non-admin users could not open a database. 
 changelog_1007_li=Non-admin users could not open a database using a mode (MODE\=xxx) if the database was already open, even if the mode matched. 
 changelog_1008_li=The SQL state of the following exceptions has been changed\: From 90009, 90010, 90011 to 22007\: "Cannot parse DATE/TIME/TIMESTAMP constant ...". 
-changelog_1009_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. There is a new system property "h2.storeLocalTime" that takes daylight time saving into account when storing and reading, however database files that are created or modified with this flag set can not be opened with older versions of H2. The new storage format is already supported for reading however, so that this version is forward compatible. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 
+changelog_1009_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used. 
 changelog_1010_h2=Version 1.3.156 (2011-06-17)
 changelog_1011_li=Issue 323\: NullPointerException when using IN(...) with a function table. 
 changelog_1012_li=Clob.toString() and Blob.toString() now include the trace identifier. 

--- a/h2/src/main/org/h2/engine/Constants.java
+++ b/h2/src/main/org/h2/engine/Constants.java
@@ -16,7 +16,7 @@ public class Constants {
    /**
     * The build date is updated for each public release.
     */
-    public static final String BUILD_DATE = "2011-06-17";
+    public static final String BUILD_DATE = "2011-06-25";

    /**
     * The build date is updated for each public release.
@@ -26,7 +26,7 @@ public class Constants {
    /**
     * The build id is incremented for each public release.
     */
-    public static final int BUILD_ID = 156;
+    public static final int BUILD_ID = 157;

    /**
     * The build id of the last stable release.

--- a/h2/src/test/org/h2/samples/newsfeed.sql
+++ b/h2/src/test/org/h2/samples/newsfeed.sql
@@ -7,6 +7,7 @@

 CREATE TABLE VERSION(ID INT PRIMARY KEY, VERSION VARCHAR, CREATED VARCHAR);
 INSERT INTO VERSION VALUES
+(107, '1.3.157', '2011-06-25'),
 (106, '1.3.156', '2011-06-17'),
 (105, '1.3.155', '2011-05-27'),
 (104, '1.3.154', '2011-04-04'),