Skip to content

H
h2database
提交 87eff5e1 authored 作者: Thomas Mueller's avatar Thomas Mueller
浏览文件
操作

Documentation.

上级 3cd15fa6
隐藏空白字符变更
内嵌 并排
正在显示 包含 165 行增加 和 140 行删除
h2/src/docsrc/html/changelog.html
浏览文件 @ 87eff5e1
...@@ -18,7 +18,7 @@ Change Log ...@@ -18,7 +18,7 @@ Change Log
<h1>Change Log</h1> <h1>Change Log</h1>
<h2>Next Version (unreleased)</h2> <h2>Next Version (unreleased)</h2>
<ul><li>- <ul><li>Deleting rows in the trigger table inside a trigger could result in a NullPointerException.
</li></ul> </li></ul>
<h2>Version 1.3.151 Beta (2011-02-12)</h2> <h2>Version 1.3.151 Beta (2011-02-12)</h2>
......
h2/src/docsrc/html/tutorial.html
浏览文件 @ 87eff5e1
...@@ -1181,6 +1181,24 @@ You can also call the index from within a Java application: ...@@ -1181,6 +1181,24 @@ You can also call the index from within a Java application:
org.h2.fulltext.FullTextLucene.search(conn, text, limit, offset); org.h2.fulltext.FullTextLucene.search(conn, text, limit, offset);
org.h2.fulltext.FullTextLucene.searchData(conn, text, limit, offset); org.h2.fulltext.FullTextLucene.searchData(conn, text, limit, offset);
</pre> </pre>
<p>
The Lucene fulltext search supports searching in specific column only.
Column names must be uppercase (except if the original columns are double quoted).
For column names starting with an underscore (_), another underscore needs to be added.
Example:
</p>
<pre>
CREATE ALIAS IF NOT EXISTS FTL_INIT FOR "org.h2.fulltext.FullTextLucene.init";
CALL FTL_INIT();
DROP TABLE IF EXISTS TEST;
CREATE TABLE TEST(ID INT PRIMARY KEY, FIRST_NAME VARCHAR, LAST_NAME VARCHAR);
CALL FTL_CREATE_INDEX('PUBLIC', 'TEST', NULL);
INSERT INTO TEST VALUES(1, 'John', 'Wayne');
INSERT INTO TEST VALUES(2, 'Elton', 'John');
SELECT * FROM FTL_SEARCH_DATA('John', 0, 0);
SELECT * FROM FTL_SEARCH_DATA('LAST_NAME:John', 0, 0);
CALL FTL_DROP_ALL();
</pre>
<h2 id="user_defined_variables">User-Defined Variables</h2> <h2 id="user_defined_variables">User-Defined Variables</h2>
<p> <p>
......
h2/src/docsrc/text/_docs_en.utf8.txt
浏览文件 @ 87eff5e1
...@@ -1526,7 +1526,7 @@ Change Log ...@@ -1526,7 +1526,7 @@ Change Log
Next Version (unreleased) Next Version (unreleased)
@changelog_1002_li @changelog_1002_li
- Deleting rows in the trigger table inside a trigger could result in a NullPointerException.
@changelog_1003_h2 @changelog_1003_h2
Version 1.3.151 Beta (2011-02-12) Version 1.3.151 Beta (2011-02-12)
...@@ -11182,138 +11182,141 @@ Using the Lucene Fulltext Search ...@@ -11182,138 +11182,141 @@ Using the Lucene Fulltext Search
@tutorial_1295_p @tutorial_1295_p
You can also call the index from within a Java application: You can also call the index from within a Java application:
@tutorial_1296_h2 @tutorial_1296_p
The Lucene fulltext search supports searching in specific column only. Column names must be uppercase (except if the original columns are double quoted). For column names starting with an underscore (_), another underscore needs to be added. Example:
@tutorial_1297_h2
User-Defined Variables User-Defined Variables
@tutorial_1297_p @tutorial_1298_p
This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command: This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command:
@tutorial_1298_p @tutorial_1299_p
The value can also be changed using the SET() method. This is useful in queries: The value can also be changed using the SET() method. This is useful in queries:
@tutorial_1299_p @tutorial_1300_p
Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well. Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well.
@tutorial_1300_h2 @tutorial_1301_h2
Date and Time Date and Time
@tutorial_1301_p @tutorial_1302_p
Date, time and timestamp values support ISO 8601 formatting, including time zone: Date, time and timestamp values support ISO 8601 formatting, including time zone:
@tutorial_1302_p @tutorial_1303_p
If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12:00:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12:00:00'. Please note that changing the time zone after the H2 driver is loaded is not supported. If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12:00:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12:00:00'. Please note that changing the time zone after the H2 driver is loaded is not supported.
@tutorial_1303_h2 @tutorial_1304_h2
Using Spring Using Spring
@tutorial_1304_p @tutorial_1305_p
Use the following configuration to start and stop the H2 TCP server using the Spring Framework: Use the following configuration to start and stop the H2 TCP server using the Spring Framework:
@tutorial_1305_p @tutorial_1306_p
The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server. The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server.
@tutorial_1306_h2 @tutorial_1307_h2
Java Management Extension (JMX) Java Management Extension (JMX)
@tutorial_1307_p @tutorial_1308_p
Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character). Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character).
@tutorial_1308_p @tutorial_1309_p
The following attributes and operations are supported: The following attributes and operations are supported:
@tutorial_1309_code @tutorial_1310_code
CacheSize CacheSize
@tutorial_1310_li @tutorial_1311_li
: the cache size currently in use in KB. : the cache size currently in use in KB.
@tutorial_1311_code @tutorial_1312_code
CacheSizeMax CacheSizeMax
@tutorial_1312_li @tutorial_1313_li
(read/write): the maximum cache size in KB. (read/write): the maximum cache size in KB.
@tutorial_1313_code @tutorial_1314_code
Exclusive Exclusive
@tutorial_1314_li @tutorial_1315_li
: whether this database is open in exclusive mode or not. : whether this database is open in exclusive mode or not.
@tutorial_1315_code @tutorial_1316_code
FileReadCount FileReadCount
@tutorial_1316_li @tutorial_1317_li
: the number of file read operations since the database was opened. : the number of file read operations since the database was opened.
@tutorial_1317_code @tutorial_1318_code
FileSize FileSize
@tutorial_1318_li @tutorial_1319_li
: the file size in KB. : the file size in KB.
@tutorial_1319_code @tutorial_1320_code
FileWriteCount FileWriteCount
@tutorial_1320_li @tutorial_1321_li
: the number of file write operations since the database was opened. : the number of file write operations since the database was opened.
@tutorial_1321_code @tutorial_1322_code
FileWriteCountTotal FileWriteCountTotal
@tutorial_1322_li @tutorial_1323_li
: the number of file write operations since the database was created. : the number of file write operations since the database was created.
@tutorial_1323_code @tutorial_1324_code
LogMode LogMode
@tutorial_1324_li @tutorial_1325_li
(read/write): the current transaction log mode. See <code>SET LOG</code> for details. (read/write): the current transaction log mode. See <code>SET LOG</code> for details.
@tutorial_1325_code @tutorial_1326_code
Mode Mode
@tutorial_1326_li @tutorial_1327_li
: the compatibility mode (<code>REGULAR</code> if no compatibility mode is used). : the compatibility mode (<code>REGULAR</code> if no compatibility mode is used).
@tutorial_1327_code @tutorial_1328_code
MultiThreaded MultiThreaded
@tutorial_1328_li @tutorial_1329_li
: true if multi-threaded is enabled. : true if multi-threaded is enabled.
@tutorial_1329_code @tutorial_1330_code
Mvcc Mvcc
@tutorial_1330_li @tutorial_1331_li
: true if <code>MVCC</code> is enabled. : true if <code>MVCC</code> is enabled.
@tutorial_1331_code @tutorial_1332_code
ReadOnly ReadOnly
@tutorial_1332_li @tutorial_1333_li
: true if the database is read-only. : true if the database is read-only.
@tutorial_1333_code @tutorial_1334_code
TraceLevel TraceLevel
@tutorial_1334_li @tutorial_1335_li
(read/write): the file trace level. (read/write): the file trace level.
@tutorial_1335_code @tutorial_1336_code
Version Version
@tutorial_1336_li @tutorial_1337_li
: the database version in use. : the database version in use.
@tutorial_1337_code @tutorial_1338_code
listSettings listSettings
@tutorial_1338_li @tutorial_1339_li
: list the database settings. : list the database settings.
@tutorial_1339_code @tutorial_1340_code
listSessions listSessions
@tutorial_1340_li @tutorial_1341_li
: list the open sessions, including currently executing statement (if any) and locked tables (if any). : list the open sessions, including currently executing statement (if any) and locked tables (if any).
h2/src/docsrc/text/_docs_ja.utf8.txt
浏览文件 @ 87eff5e1
...@@ -1526,7 +1526,7 @@ Centralリポジトリの利用 ...@@ -1526,7 +1526,7 @@ Centralリポジトリの利用
#Next Version (unreleased) #Next Version (unreleased)
@changelog_1002_li @changelog_1002_li
#- #Deleting rows in the trigger table inside a trigger could result in a NullPointerException.
@changelog_1003_h2 @changelog_1003_h2
#Version 1.3.151 Beta (2011-02-12) #Version 1.3.151 Beta (2011-02-12)
...@@ -11182,138 +11182,141 @@ Luceneフルテキストサーチを使用する ...@@ -11182,138 +11182,141 @@ Luceneフルテキストサーチを使用する
@tutorial_1295_p @tutorial_1295_p
# You can also call the index from within a Java application: # You can also call the index from within a Java application:
@tutorial_1296_h2 @tutorial_1296_p
# The Lucene fulltext search supports searching in specific column only. Column names must be uppercase (except if the original columns are double quoted). For column names starting with an underscore (_), another underscore needs to be added. Example:
@tutorial_1297_h2
#User-Defined Variables #User-Defined Variables
@tutorial_1297_p @tutorial_1298_p
# This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command: # This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command:
@tutorial_1298_p @tutorial_1299_p
# The value can also be changed using the SET() method. This is useful in queries: # The value can also be changed using the SET() method. This is useful in queries:
@tutorial_1299_p @tutorial_1300_p
# Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well. # Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well.
@tutorial_1300_h2 @tutorial_1301_h2
#Date and Time #Date and Time
@tutorial_1301_p @tutorial_1302_p
# Date, time and timestamp values support ISO 8601 formatting, including time zone: # Date, time and timestamp values support ISO 8601 formatting, including time zone:
@tutorial_1302_p @tutorial_1303_p
# If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12:00:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12:00:00'. Please note that changing the time zone after the H2 driver is loaded is not supported. # If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12:00:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12:00:00'. Please note that changing the time zone after the H2 driver is loaded is not supported.
@tutorial_1303_h2 @tutorial_1304_h2
#Using Spring #Using Spring
@tutorial_1304_p @tutorial_1305_p
# Use the following configuration to start and stop the H2 TCP server using the Spring Framework: # Use the following configuration to start and stop the H2 TCP server using the Spring Framework:
@tutorial_1305_p @tutorial_1306_p
# The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server. # The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server.
@tutorial_1306_h2 @tutorial_1307_h2
#Java Management Extension (JMX) #Java Management Extension (JMX)
@tutorial_1307_p @tutorial_1308_p
# Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character). # Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character).
@tutorial_1308_p @tutorial_1309_p
# The following attributes and operations are supported: # The following attributes and operations are supported:
@tutorial_1309_code @tutorial_1310_code
#CacheSize #CacheSize
@tutorial_1310_li @tutorial_1311_li
#: the cache size currently in use in KB. #: the cache size currently in use in KB.
@tutorial_1311_code @tutorial_1312_code
#CacheSizeMax #CacheSizeMax
@tutorial_1312_li @tutorial_1313_li
# (read/write): the maximum cache size in KB. # (read/write): the maximum cache size in KB.
@tutorial_1313_code @tutorial_1314_code
#Exclusive #Exclusive
@tutorial_1314_li @tutorial_1315_li
#: whether this database is open in exclusive mode or not. #: whether this database is open in exclusive mode or not.
@tutorial_1315_code @tutorial_1316_code
#FileReadCount #FileReadCount
@tutorial_1316_li @tutorial_1317_li
#: the number of file read operations since the database was opened. #: the number of file read operations since the database was opened.
@tutorial_1317_code @tutorial_1318_code
#FileSize #FileSize
@tutorial_1318_li @tutorial_1319_li
#: the file size in KB. #: the file size in KB.
@tutorial_1319_code @tutorial_1320_code
#FileWriteCount #FileWriteCount
@tutorial_1320_li @tutorial_1321_li
#: the number of file write operations since the database was opened. #: the number of file write operations since the database was opened.
@tutorial_1321_code @tutorial_1322_code
#FileWriteCountTotal #FileWriteCountTotal
@tutorial_1322_li @tutorial_1323_li
#: the number of file write operations since the database was created. #: the number of file write operations since the database was created.
@tutorial_1323_code @tutorial_1324_code
#LogMode #LogMode
@tutorial_1324_li @tutorial_1325_li
# (read/write): the current transaction log mode. See <code>SET LOG</code> for details. # (read/write): the current transaction log mode. See <code>SET LOG</code> for details.
@tutorial_1325_code @tutorial_1326_code
#Mode #Mode
@tutorial_1326_li @tutorial_1327_li
#: the compatibility mode (<code>REGULAR</code> if no compatibility mode is used). #: the compatibility mode (<code>REGULAR</code> if no compatibility mode is used).
@tutorial_1327_code @tutorial_1328_code
#MultiThreaded #MultiThreaded
@tutorial_1328_li @tutorial_1329_li
#: true if multi-threaded is enabled. #: true if multi-threaded is enabled.
@tutorial_1329_code @tutorial_1330_code
#Mvcc #Mvcc
@tutorial_1330_li @tutorial_1331_li
#: true if <code>MVCC</code> is enabled. #: true if <code>MVCC</code> is enabled.
@tutorial_1331_code @tutorial_1332_code
#ReadOnly #ReadOnly
@tutorial_1332_li @tutorial_1333_li
#: true if the database is read-only. #: true if the database is read-only.
@tutorial_1333_code @tutorial_1334_code
#TraceLevel #TraceLevel
@tutorial_1334_li @tutorial_1335_li
# (read/write): the file trace level. # (read/write): the file trace level.
@tutorial_1335_code @tutorial_1336_code
#Version #Version
@tutorial_1336_li @tutorial_1337_li
#: the database version in use. #: the database version in use.
@tutorial_1337_code @tutorial_1338_code
#listSettings #listSettings
@tutorial_1338_li @tutorial_1339_li
#: list the database settings. #: list the database settings.
@tutorial_1339_code @tutorial_1340_code
#listSessions #listSessions
@tutorial_1340_li @tutorial_1341_li
#: list the open sessions, including currently executing statement (if any) and locked tables (if any). #: list the open sessions, including currently executing statement (if any) and locked tables (if any).
h2/src/docsrc/textbase/_docs_en.properties
浏览文件 @ 87eff5e1
...@@ -507,7 +507,7 @@ build_1096_li=The rail images (one straight, four junctions, two turns) are gene ...@@ -507,7 +507,7 @@ build_1096_li=The rail images (one straight, four junctions, two turns) are gene
build_1097_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification. build_1097_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
changelog_1000_h1=Change Log changelog_1000_h1=Change Log
changelog_1001_h2=Next Version (unreleased) changelog_1001_h2=Next Version (unreleased)
changelog_1002_li=- changelog_1002_li=Deleting rows in the trigger table inside a trigger could result in a NullPointerException.
changelog_1003_h2=Version 1.3.151 Beta (2011-02-12) changelog_1003_h2=Version 1.3.151 Beta (2011-02-12)
changelog_1004_li=Server\: it was possible to open a database outside of the base URL (if one was set). The test case was broken. changelog_1004_li=Server\: it was possible to open a database outside of the base URL (if one was set). The test case was broken.
changelog_1005_li=The H2 Console tool now supports a database URL as a command line option. changelog_1005_li=The H2 Console tool now supports a database URL as a command line option.
...@@ -3726,48 +3726,49 @@ tutorial_1292_p=\ PUBLIC is the schema name, TEST is the table name. The list of ...@@ -3726,48 +3726,49 @@ tutorial_1292_p=\ PUBLIC is the schema name, TEST is the table name. The list of
tutorial_1293_p=\ This will produce a result set that contains the query needed to retrieve the data\: tutorial_1293_p=\ This will produce a result set that contains the query needed to retrieve the data\:
tutorial_1294_p=\ To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code>. The result contains the columns <code>SCHEMA</code> (the schema name), <code>TABLE</code> (the table name), <code>COLUMNS</code> (an array of column names), and <code>KEYS</code> (an array of objects). To join a table, use a join as in\: <code>SELECT T.* FROM FTL_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE\='TEST' AND T.ID\=FT.KEYS[0];</code> tutorial_1294_p=\ To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code>. The result contains the columns <code>SCHEMA</code> (the schema name), <code>TABLE</code> (the table name), <code>COLUMNS</code> (an array of column names), and <code>KEYS</code> (an array of objects). To join a table, use a join as in\: <code>SELECT T.* FROM FTL_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE\='TEST' AND T.ID\=FT.KEYS[0];</code>
tutorial_1295_p=\ You can also call the index from within a Java application\: tutorial_1295_p=\ You can also call the index from within a Java application\:
tutorial_1296_h2=User-Defined Variables tutorial_1296_p=\ The Lucene fulltext search supports searching in specific column only. Column names must be uppercase (except if the original columns are double quoted). For column names starting with an underscore (_), another underscore needs to be added. Example\:
tutorial_1297_p=\ This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command\: tutorial_1297_h2=User-Defined Variables
tutorial_1298_p=\ The value can also be changed using the SET() method. This is useful in queries\: tutorial_1298_p=\ This database supports user-defined variables. Variables start with <code>@</code> and can be used wherever expressions or parameters are allowed. Variables are not persisted and session scoped, that means only visible from within the session in which they are defined. A value is usually assigned using the SET command\:
tutorial_1299_p=\ Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well. tutorial_1299_p=\ The value can also be changed using the SET() method. This is useful in queries\:
tutorial_1300_h2=Date and Time tutorial_1300_p=\ Variables that are not set evaluate to <code>NULL</code>. The data type of a user-defined variable is the data type of the value assigned to it, that means it is not necessary (or possible) to declare variable names before using them. There are no restrictions on the assigned values; large objects (LOBs) are supported as well.
tutorial_1301_p=\ Date, time and timestamp values support ISO 8601 formatting, including time zone\: tutorial_1301_h2=Date and Time
tutorial_1302_p=\ If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12\:00\:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12\:00\:00'. Please note that changing the time zone after the H2 driver is loaded is not supported. tutorial_1302_p=\ Date, time and timestamp values support ISO 8601 formatting, including time zone\:
tutorial_1303_h2=Using Spring tutorial_1303_p=\ If the time zone is not set, the value is parsed using the current time zone setting of the system. Date and time information is stored in H2 database files without time zone information. If the database is opened using another system time zone, the date and time will be the same. That means if you store the value '2000-01-01 12\:00\:00' in one time zone, then close the database and open the database again in a different time zone, you will also get '2000-01-01 12\:00\:00'. Please note that changing the time zone after the H2 driver is loaded is not supported.
tutorial_1304_p=\ Use the following configuration to start and stop the H2 TCP server using the Spring Framework\: tutorial_1304_h2=Using Spring
tutorial_1305_p=\ The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server. tutorial_1305_p=\ Use the following configuration to start and stop the H2 TCP server using the Spring Framework\:
tutorial_1306_h2=Java Management Extension (JMX) tutorial_1306_p=\ The <code>destroy-method</code> will help prevent exceptions on hot-redeployment or when restarting the server.
tutorial_1307_p=\ Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX\=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character). tutorial_1307_h2=Java Management Extension (JMX)
tutorial_1308_p=\ The following attributes and operations are supported\: tutorial_1308_p=\ Management over JMX is supported, but not enabled by default. To enable JMX, append <code>;JMX\=TRUE</code> to the database URL when opening the database. Various tools support JMX, one such tool is the <code>jconsole</code>. When opening the <code>jconsole</code>, connect to the process where the database is open (when using the server mode, you need to connect to the server process). Then go to the <code>MBeans</code> section. Under <code>org.h2</code> you will find one entry per database. The object name of the entry is the database short name, plus the path (each colon is replaced with an underscore character).
tutorial_1309_code=CacheSize tutorial_1309_p=\ The following attributes and operations are supported\:
tutorial_1310_li=\: the cache size currently in use in KB. tutorial_1310_code=CacheSize
tutorial_1311_code=CacheSizeMax tutorial_1311_li=\: the cache size currently in use in KB.
tutorial_1312_li=\ (read/write)\: the maximum cache size in KB. tutorial_1312_code=CacheSizeMax
tutorial_1313_code=Exclusive tutorial_1313_li=\ (read/write)\: the maximum cache size in KB.
tutorial_1314_li=\: whether this database is open in exclusive mode or not. tutorial_1314_code=Exclusive
tutorial_1315_code=FileReadCount tutorial_1315_li=\: whether this database is open in exclusive mode or not.
tutorial_1316_li=\: the number of file read operations since the database was opened. tutorial_1316_code=FileReadCount
tutorial_1317_code=FileSize tutorial_1317_li=\: the number of file read operations since the database was opened.
tutorial_1318_li=\: the file size in KB. tutorial_1318_code=FileSize
tutorial_1319_code=FileWriteCount tutorial_1319_li=\: the file size in KB.
tutorial_1320_li=\: the number of file write operations since the database was opened. tutorial_1320_code=FileWriteCount
tutorial_1321_code=FileWriteCountTotal tutorial_1321_li=\: the number of file write operations since the database was opened.
tutorial_1322_li=\: the number of file write operations since the database was created. tutorial_1322_code=FileWriteCountTotal
tutorial_1323_code=LogMode tutorial_1323_li=\: the number of file write operations since the database was created.
tutorial_1324_li=\ (read/write)\: the current transaction log mode. See <code>SET LOG</code> for details. tutorial_1324_code=LogMode
tutorial_1325_code=Mode tutorial_1325_li=\ (read/write)\: the current transaction log mode. See <code>SET LOG</code> for details.
tutorial_1326_li=\: the compatibility mode (<code>REGULAR</code> if no compatibility mode is used). tutorial_1326_code=Mode
tutorial_1327_code=MultiThreaded tutorial_1327_li=\: the compatibility mode (<code>REGULAR</code> if no compatibility mode is used).
tutorial_1328_li=\: true if multi-threaded is enabled. tutorial_1328_code=MultiThreaded
tutorial_1329_code=Mvcc tutorial_1329_li=\: true if multi-threaded is enabled.
tutorial_1330_li=\: true if <code>MVCC</code> is enabled. tutorial_1330_code=Mvcc
tutorial_1331_code=ReadOnly tutorial_1331_li=\: true if <code>MVCC</code> is enabled.
tutorial_1332_li=\: true if the database is read-only. tutorial_1332_code=ReadOnly
tutorial_1333_code=TraceLevel tutorial_1333_li=\: true if the database is read-only.
tutorial_1334_li=\ (read/write)\: the file trace level. tutorial_1334_code=TraceLevel
tutorial_1335_code=Version tutorial_1335_li=\ (read/write)\: the file trace level.
tutorial_1336_li=\: the database version in use. tutorial_1336_code=Version
tutorial_1337_code=listSettings tutorial_1337_li=\: the database version in use.
tutorial_1338_li=\: list the database settings. tutorial_1338_code=listSettings
tutorial_1339_code=listSessions tutorial_1339_li=\: list the database settings.
tutorial_1340_li=\: list the open sessions, including currently executing statement (if any) and locked tables (if any). tutorial_1340_code=listSessions
tutorial_1341_li=\: list the open sessions, including currently executing statement (if any) and locked tables (if any).
h2/src/tools/org/h2/build/doc/dictionary.txt
浏览文件 @ 87eff5e1
...@@ -669,4 +669,4 @@ ooq exceeded eye hannibal stels garringer czech prevention propagate ...@@ -669,4 +669,4 @@ ooq exceeded eye hannibal stels garringer czech prevention propagate
compromise portion nodded rapping door stealing napping artifacts lore compromise portion nodded rapping door stealing napping artifacts lore
pondered curious muttered quaint chamber nearly unwrapped flows weary volume pondered curious muttered quaint chamber nearly unwrapped flows weary volume
tapping gently dreary wrapping tis moger udt chafik outfile geom scalable tapping gently dreary wrapping tis moger udt chafik outfile geom scalable
highly cloud infrastructure highly cloud infrastructure elton wayne
Markdown 格式
0% 或
您添加了 0 人 到此讨论。请谨慎行事。
请先完成此评论的编辑！
请 注册 或者 后发表评论