提交 ca13091b authored 作者: Thomas Mueller's avatar Thomas Mueller

Prepare release.

上级 7ae16cdd
......@@ -18,6 +18,10 @@ Change Log
<h1>Change Log</h1>
<h2>Next Version (unreleased)</h2>
<ul><li>-
</li></ul>
<h2>Version 1.3.160 (2011-09-11)</h2>
<ul><li>Computed columns could not refer to itself.
</li><li>Issue 340: Comparison with "x = all(select ...)" or similar in a view or
subquery that was used as a table returned the wrong result.
......@@ -765,48 +769,5 @@ Change Log
or unlocking is not working).
</li></ul>
<h2>Version 1.2.141 (2010-08-22)</h2>
<ul><li>New experimental pseudo-encryption algorithm "FOG".
It makes the data appear to be encrypted. This algorithm is cryptographically extremely weak,
and should only be used to hide data from reading the plain text using a text editor.
Please let us know if you think this is useful or not.
</li><li>Documentation: the grammar and function documentation can now be easier translated.
</li><li>Password hash: in addition to connecting with the plain text password,
H2 now supports connecting with the password hash.
Like this you don't have to store plain text passwords in config files.
For details, see the documentation at Advanced / Password Hash.
</li><li>Lucene 3.x support was added in the source code, however it is not yet enabled by default
and is not yet supported when using the default h2 jar file. To enable Lucene 3.x support,
the source code of H2 needs to be switched using <code>./build.sh -Dlucene=3 switchSource</code>,
and then re-compile. To switch the source code back use <code>./build.sh -Dlucene=2 switchSource</code> (replace
./build.sh with build.bat on Windows).
The plan is to use Lucene 3 by default in H2 version 1.3.x.
Issue 147.
</li><li>The native fulltext search could cause a Java level deadlock if searching from multiple connections concurrently.
</li><li>CREATE FORCE VIEW didn't work in most cases if a referenced table didn't exist.
</li><li>MVCC: when trying to insert two rows with the same key from two connections,
the second connection immediately threw the exception "Unique index or primary key violation".
Instead, the second connection now waits throwing the exception until the first connection
committed the change (same as when trying to concurrently update the same row).
</li><li>Server mode: if the client ran with a different timezone setting than the server, date values
got shifted by the difference between the timezones. This problem affected the data types
DATE, TIME, and TIMESTAMP, when using PreparedStatement.setDate / setTime / setTimestamp
and ResultSet.getDate / getTime / getTimestamp.
To solve the problem, both the client and the server need to be updated (otherwise the old transfer protocol is used).
</li><li>The built-in connection pool (JdbcConnectionPool) did not always honor the login timeout
(the timeout could occur much too early). Thanks a lot to Dario Fassi for the patch!
</li><li>Translation: the new messages have been translated to Spanish. Thanks a lot to Dario Fassi!
</li><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>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).
</li><li>The command line tools now say so if the source directory of an option doesn't exist.
</li><li>It is now allowed to truncate a table if referential integrity has been disabled for this table or database.
</li><li>For unencrypted databases, the automatic upgrade temporary script file is now unencrypted again.
</li></ul>
<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>
......@@ -16,22 +16,22 @@ public class Constants {
/**
* The build date is updated for each public release.
*/
public static final String BUILD_DATE = "2011-08-13";
public static final String BUILD_DATE = "2011-09-11";
/**
* The build date is updated for each public release.
*/
public static final String BUILD_DATE_STABLE = "2011-07-17";
public static final String BUILD_DATE_STABLE = "2011-08-13";
/**
* The build id is incremented for each public release.
*/
public static final int BUILD_ID = 159;
public static final int BUILD_ID = 160;
/**
* The build id of the last stable release.
*/
public static final int BUILD_ID_STABLE = 158;
public static final int BUILD_ID_STABLE = 159;
/**
* If H2 is compiled to be included in a product, this should be set to
......
......@@ -7,6 +7,7 @@
CREATE TABLE VERSION(ID INT PRIMARY KEY, VERSION VARCHAR, CREATED VARCHAR);
INSERT INTO VERSION VALUES
(110, '1.3.160', '2011-09-11'),
(109, '1.3.159', '2011-08-13'),
(108, '1.3.158', '2011-07-17'),
(107, '1.3.157', '2011-06-25'),
......@@ -23,9 +24,7 @@ INSERT INTO VERSION VALUES
(96, '1.3.146 Beta', '2010-11-08'),
(95, '1.2.145', '2010-11-02'),
(94, '1.2.144', '2010-10-15'),
(93, '1.2.143', '2010-09-18'),
(92, '1.2.142', '2010-08-31'),
(91, '1.2.141', '2010-08-22'),
(93, '1.2.143', '2010-09-18')
;
CREATE TABLE CHANNEL(TITLE VARCHAR, LINK VARCHAR, DESC VARCHAR,
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论