提交 7e6af760 authored 作者: Thomas Mueller's avatar Thomas Mueller

Documentation.

上级 49207ecb
...@@ -31,13 +31,13 @@ Change Log ...@@ -31,13 +31,13 @@ Change Log
</li><li>The INSERT optimizations (INSERT ... DIRECT SORTED SELECT) were not parsed correctly when using a column list. </li><li>The INSERT optimizations (INSERT ... DIRECT SORTED SELECT) were not parsed correctly when using a column list.
</li><li>H2 Console: the tables and columns are now listed for SQLite as well. </li><li>H2 Console: the tables and columns are now listed for SQLite as well.
</li><li>H2 Console: improved autocomplete feature (also simplified the source code for this feature). </li><li>H2 Console: improved autocomplete feature (also simplified the source code for this feature).
</li><li>The DbStarter servlet context listener now starts the server before opening a connection, </li><li>Issue 260: the DbStarter servlet context listener now starts the server before opening a connection,
so that connecting using the server mode works. so that connecting using the server mode works.
</li><li>The Shell tool can now enable, disable, and display the current autocommit mode. </li><li>The Shell tool can now enable, disable, and display the current autocommit mode.
</li><li>There is a limitation in the cluster mode: </li><li>Issue 259: there is a limitation in the cluster mode:
The SQL statement SET AUTOCOMMIT FALSE doesn't work. The SQL statement SET AUTOCOMMIT FALSE doesn't work.
To disable autocommit, the method Connection.setAutoCommit(false) needs to be called. To disable autocommit, the method Connection.setAutoCommit(false) needs to be called.
This is now documented. See also issue 259. This is now documented.
</li><li>Connection pool / DataSource: a NullPointerException was thrown when </li><li>Connection pool / DataSource: a NullPointerException was thrown when
using a database URL that doesn't start with "jdbc:h2:". using a database URL that doesn't start with "jdbc:h2:".
</li><li>Using the java.sql.Blob or java.sql.Clob interfaces could throw the wrong </li><li>Using the java.sql.Blob or java.sql.Clob interfaces could throw the wrong
...@@ -74,7 +74,7 @@ when "LOBs in database" is enabled). ...@@ -74,7 +74,7 @@ when "LOBs in database" is enabled).
</li><li>When concurrently preparing many statements with a subquery, in some cases the query didn't run </li><li>When concurrently preparing many statements with a subquery, in some cases the query didn't run
(Column "..." must be in the GROUP BY list). (Column "..." must be in the GROUP BY list).
</li><li>CallableStatement: now the syntax "{? = CALL...}" is supported as well. </li><li>CallableStatement: now the syntax "{? = CALL...}" is supported as well.
</li><li>Lob in databases: two small BLOB or CLOB values were always considered equal. </li><li>Issue Lob in databases: two small BLOB or CLOB values were always considered equal.
This also affected unique indexes. This also affected unique indexes.
</li><li>The shutdown hook is (re-) enabled by default even for H2 version 1.3.x. </li><li>The shutdown hook is (re-) enabled by default even for H2 version 1.3.x.
</li><li>When creating a database from a recovery script, the same user can now be used </li><li>When creating a database from a recovery script, the same user can now be used
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论