提交 67e6312d authored 作者: Thomas Mueller's avatar Thomas Mueller

Documentation.

上级 792d9e8e
...@@ -18,7 +18,13 @@ Change Log ...@@ -18,7 +18,13 @@ Change Log
<h1>Change Log</h1> <h1>Change Log</h1>
<h2>Next Version (unreleased)</h2> <h2>Next Version (unreleased)</h2>
<ul><li>New experimental feature to speed up CREATE TABLE ... AS SELECT. <ul><li>The index condition columnName IS NULL was not efficient when using a clustered index.
</li><li>The Recover tool did not work for databases larger than 2 GB.
</li><li>In memory database: outer joins with a condition "column is null" could return the wrong result.
</li><li>Temporary files were not created in the temporary directory of the system, but in the current working directory.
This affected temporary undo log files for read-only databases, temporary files for large result sets when using read-only databases,
and temporary lob files when storing LOBs in the database (system property h2.lobInDatabase).
</li><li>New experimental feature to speed up CREATE TABLE ... AS SELECT.
To enable the feature, set the system property h2.optimizeInsertFromSelect to true. To enable the feature, set the system property h2.optimizeInsertFromSelect to true.
For large queries, performance can be doubled. For large queries, performance can be doubled.
</li><li>When LOB objects are stored in the database (using the experimental setting h2.lobInDatabase), </li><li>When LOB objects are stored in the database (using the experimental setting h2.lobInDatabase),
......
...@@ -288,7 +288,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>. ...@@ -288,7 +288,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>MySQL compatibility: real SQL statement for DESCRIBE TEST </li><li>MySQL compatibility: real SQL statement for DESCRIBE TEST
</li><li>Use a default delay of 1 second before closing a database. </li><li>Use a default delay of 1 second before closing a database.
</li><li>Write (log) to system table before adding to internal data structures. </li><li>Write (log) to system table before adding to internal data structures.
</li><li>Support very large deletes and updates. </li><li>Support opening a database that is in the classpath, maybe using a new file system.
</li><li>Doclet (javadocs): constructors are not listed. </li><li>Doclet (javadocs): constructors are not listed.
</li><li>Support direct lookup for MIN and MAX when using WHERE (see todo.txt / Direct Lookup). </li><li>Support direct lookup for MIN and MAX when using WHERE (see todo.txt / Direct Lookup).
</li><li>Support other array types (String[], double[]) in PreparedStatement.setObject(int, Object); </li><li>Support other array types (String[], double[]) in PreparedStatement.setObject(int, Object);
...@@ -329,7 +329,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>. ...@@ -329,7 +329,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>AUTO_SERVER: support changing IP addresses (disable a network while the database is open). </li><li>AUTO_SERVER: support changing IP addresses (disable a network while the database is open).
</li><li>Avoid using java.util.Calendar internally because it's slow, complicated, and buggy. </li><li>Avoid using java.util.Calendar internally because it's slow, complicated, and buggy.
</li><li>Support TRUNCATE .. CASCADE like PostgreSQL. </li><li>Support TRUNCATE .. CASCADE like PostgreSQL.
</li><li>Support opening a database that is in the classpath, maybe using a new file system.
</li><li>Fulltext search: lazy result generation using SimpleRowSource. </li><li>Fulltext search: lazy result generation using SimpleRowSource.
</li><li>Support transformation to join for user defined functions, as for IN(SELECT...). </li><li>Support transformation to join for user defined functions, as for IN(SELECT...).
</li><li>Fulltext search: support alternative syntax: WHERE FTL_CONTAINS(name, 'hello'). </li><li>Fulltext search: support alternative syntax: WHERE FTL_CONTAINS(name, 'hello').
...@@ -343,6 +342,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>. ...@@ -343,6 +342,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>MySQL, HSQLDB compatibility: support where 'a'=1 (not supported by Derby, PostgreSQL) </li><li>MySQL, HSQLDB compatibility: support where 'a'=1 (not supported by Derby, PostgreSQL)
</li><li>Allow calling function with no parameters without parenthesis. See http://code.google.com/p/h2database/issues/detail?id=50 </li><li>Allow calling function with no parameters without parenthesis. See http://code.google.com/p/h2database/issues/detail?id=50
</li><li>CSV: currently # is a line comment and can start at any field. Make it optional. </li><li>CSV: currently # is a line comment and can start at any field. Make it optional.
</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>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>Add database creation date and time to the database.
</li><li>Support ASSERTION. </li><li>Support ASSERTION.
...@@ -469,7 +469,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>. ...@@ -469,7 +469,6 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>Issue 179: Related subqueries in HAVING clause </li><li>Issue 179: Related subqueries in HAVING clause
</li><li>IBM DB2 compatibility: NOT NULL WITH DEFAULT. Similar to MySQL Mode.convertInsertNullToZero. </li><li>IBM DB2 compatibility: NOT NULL WITH DEFAULT. Similar to MySQL Mode.convertInsertNullToZero.
</li><li>Creating primary key: always create a constraint. </li><li>Creating primary key: always create a constraint.
</li><li>Support a data type "timestamp with timezone" using java.util.Calendar.
</li><li>Maybe use a different page layout: keep the data at the head of the page, and ignore the tail </li><li>Maybe use a different page layout: keep the data at the head of the page, and ignore the tail
(don't store / read it). This may increase write / read performance depending on the file system. (don't store / read it). This may increase write / read performance depending on the file system.
</li><li>Indexes of temporary tables are currently kept in-memory. Is this how it should be? </li><li>Indexes of temporary tables are currently kept in-memory. Is this how it should be?
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论