@@ -851,7 +851,7 @@ To disable anonymous SSL, set the system property <code>h2.enableAnonymousSSL</c
Universally Unique Identifiers (UUID)
@advanced_1284_p
This database supports the UUIDs. Also supported is a function to create new UUIDs using a cryptographically strong pseudo random number generator. With random UUIDs, the chance of two having the same value can be calculated using the probability theory. See also 'Birthday Paradox'. Standardized randomly generated UUIDs have 122 random bits. 4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz). This database supports generating such UUIDs using the built-in function RANDOM_UUID(). Here is a small program to estimate the probability of having two identical UUIDs after generating a number of values:
This database supports UUIDs. Also supported is a function to create new UUIDs using a cryptographically strong pseudo random number generator. With random UUIDs, the chance of two having the same value can be calculated using the probability theory. See also 'Birthday Paradox'. Standardized randomly generated UUIDs have 122 random bits. 4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz). This database supports generating such UUIDs using the built-in function RANDOM_UUID(). Here is a small program to estimate the probability of having two identical UUIDs after generating a number of values:
@advanced_1285_p
Some values are:
...
...
@@ -9031,13 +9031,19 @@ Fast alter table add column.
@roadmap_1421_li
Improve concurrency for in-memory database operations.
@roadmap_1422_h2
Not Planned
@roadmap_1422_li
Issue 122: Support for connection aliases for remote tcp connections.
@roadmap_1423_li
Fast scrambling (strong encryption doesn't help if the password is included in the application).
@roadmap_1424_h2
Not Planned
@roadmap_1425_li
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1424_li
@roadmap_1426_li
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
<a href="javascript:select('details')" id = "detailsTab">Details</a> <a href="javascript:select('source')" id = "sourceTab">Source Code</a>
@sourceError_1004_p
Fill in the error message and stack trace and click on 'Details' or 'Source Code':
...
...
@@ -9683,7 +9689,7 @@ This will produce a result set that contains the query needed to retrieve the da
QUERY: "PUBLIC"."TEST" WHERE "ID"=1
@tutorial_1201_p
To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in: <code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE='TEST' AND T.ID=FT.KEYS[0];</code>
To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in: <code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE='TEST' AND T.ID=FT.KEYS[0];</code>
@tutorial_1202_p
You can also call the index from within a Java application:
...
...
@@ -9707,7 +9713,7 @@ This will produce a result set that contains the query needed to retrieve the da
QUERY: "PUBLIC"."TEST" WHERE "ID"=1
@tutorial_1209_p
To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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>
To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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_1210_p
You can also call the index from within a Java application:
#This database supports UUIDs. Also supported is a function to create new UUIDs using a cryptographically strong pseudo random number generator. With random UUIDs, the chance of two having the same value can be calculated using the probability theory. See also 'Birthday Paradox'. Standardized randomly generated UUIDs have 122 random bits. 4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz). This database supports generating such UUIDs using the built-in function RANDOM_UUID(). Here is a small program to estimate the probability of having two identical UUIDs after generating a number of values:
@advanced_1285_p
いくつかの値は:
...
...
@@ -9031,13 +9031,19 @@ SQLコマンドがコマンドエリアに表示されます。
@roadmap_1421_li
#Improve concurrency for in-memory database operations.
@roadmap_1422_h2
#Not Planned
@roadmap_1422_li
#Issue 122: Support for connection aliases for remote tcp connections.
@roadmap_1423_li
#Fast scrambling (strong encryption doesn't help if the password is included in the application).
@roadmap_1424_h2
#Not Planned
@roadmap_1425_li
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1424_li
@roadmap_1426_li
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
#To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in: <code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE='TEST' AND T.ID=FT.KEYS[0];</code>
#To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in: <code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE='TEST' AND T.ID=FT.KEYS[0];</code>
@tutorial_1202_p
Javaアプリケーション内からインデックスを呼び出すことも可能です:
...
...
@@ -9707,7 +9713,7 @@ Luceneフルテキストサーチを使用する
#QUERY: "PUBLIC"."TEST" WHERE "ID"=1
@tutorial_1209_p
#To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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>
#To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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>
@@ -282,7 +282,7 @@ advanced_1280_p=Remote SSL/TLS connections are supported using the Java Secure S
advanced_1281_p=To use your own keystore, set the system properties <code>javax.net.ssl.keyStore</code> and <code>javax.net.ssl.keyStorePassword</code> before starting the H2 server and client. See also <a href\="http\://java.sun.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html\#CustomizingStores">Customizing the Default Key and Trust Stores, Store Types, and Store Passwords</a> for more information.
advanced_1282_p=To disable anonymous SSL, set the system property <code>h2.enableAnonymousSSL</code> to false.
advanced_1284_p=This database supports the UUIDs. Also supported is a function to create new UUIDs using a cryptographically strong pseudo random number generator. With random UUIDs, the chance of two having the same value can be calculated using the probability theory. See also 'Birthday Paradox'. Standardized randomly generated UUIDs have 122 random bits. 4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz). This database supports generating such UUIDs using the built-in function RANDOM_UUID(). Here is a small program to estimate the probability of having two identical UUIDs after generating a number of values\:
advanced_1284_p=This database supports UUIDs. Also supported is a function to create new UUIDs using a cryptographically strong pseudo random number generator. With random UUIDs, the chance of two having the same value can be calculated using the probability theory. See also 'Birthday Paradox'. Standardized randomly generated UUIDs have 122 random bits. 4 bits are used for the version (Randomly generated UUID), and 2 bits for the variant (Leach-Salz). This database supports generating such UUIDs using the built-in function RANDOM_UUID(). Here is a small program to estimate the probability of having two identical UUIDs after generating a number of values\:
advanced_1285_p=Some values are\:
advanced_1286_p=To help non-mathematicians understand what those numbers mean, here a comparison\:one's annual risk of being hit by a meteorite is estimated to be one chance in 17 billion, that means the probability is about 0.000'000'000'06.
advanced_1287_h2=Settings Read from System Properties
...
...
@@ -3007,13 +3007,15 @@ roadmap_1418_li=Add option to enable TCP_NODELAY using Socket.setTcpNoDelay(true
roadmap_1419_li=Maybe disallow \=within database names (jdbc\:h2\:mem\:MODE\=DB2 means database name MODE\=DB2).
roadmap_1420_li=Fast alter table add column.
roadmap_1421_li=Improve concurrency for in-memory database operations.
roadmap_1422_h2=Not Planned
roadmap_1423_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1424_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
roadmap_1422_li=Issue 122\:Support for connection aliases for remote tcp connections.
roadmap_1423_li=Fast scrambling (strong encryption doesn't help if the password is included in the application).
roadmap_1424_h2=Not Planned
roadmap_1425_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1426_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
sourceError_1004_p=Fill in the error message and stack trace and click on 'Details' or 'Source Code'\:
sourceError_1005_b=Error Code\:
sourceError_1006_b=Product Version\:
...
...
@@ -3224,7 +3226,7 @@ tutorial_1197_p=You need to initialize it in each database where you want to use
tutorial_1198_p=PUBLIC is the schema, TEST is the table name. The list of column names (column separated) is optional, in this case all columns are indexed. The index is updated in realtime. To search the index, use the following query\:
tutorial_1199_p=This will produce a result set that contains the query needed to retrieve the data\:
tutorial_1200_p=QUERY\:"PUBLIC"."TEST" WHERE "ID"\=1
tutorial_1201_p=To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in\:<code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE\='TEST'AND T.ID\=FT.KEYS[0];</code>
tutorial_1201_p=To get the raw data, use <code>FT_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (an array of objects). To join a table, use a join as in\:<code>SELECT T.* FROM FT_SEARCH_DATA('Hello', 0, 0) FT, TEST T WHERE FT.TABLE\='TEST'AND T.ID\=FT.KEYS[0];</code>
tutorial_1202_p=You can also call the index from within a Java application\:
tutorial_1203_h3=Using the Lucene Fulltext Search
tutorial_1204_p=To use the Lucene full text search, you need the Lucene library in the classpath. How to do that depends on the application; if you use the H2 Console, you can add the Lucene jar file to the environment variables H2DRIVERS or CLASSPATH. To initialize the Lucene fulltext search in a database, call\:
...
...
@@ -3232,7 +3234,7 @@ tutorial_1205_p=You need to initialize it in each database where you want to use
tutorial_1206_p=PUBLIC is the schema, TEST is the table name. The list of column names (column separated) is optional, in this case all columns are indexed. The index is updated in realtime. To search the index, use the following query\:
tutorial_1207_p=This will produce a result set that contains the query needed to retrieve the data\:
tutorial_1208_p=QUERY\:"PUBLIC"."TEST" WHERE "ID"\=1
tutorial_1209_p=To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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_1209_p=To get the raw data, use <code>FTL_SEARCH_DATA('Hello', 0, 0);</code> . The result contains the columns SCHEMA (the schema name), TABLE (the table name), COLUMNS (an array of column names), and KEYS (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_1210_p=You can also call the index from within a Java application\:
tutorial_1211_h2=User-Defined Variables
tutorial_1212_p=This database supports user-defined variables. Variables start with @ 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\:
