trafodion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From li...@apache.org
Subject [1/3] trafodion git commit: Add Considerations for *CREATE INDEX Statement* in *Trafodion SQL Reference Manual* and Fix Typos
Date Fri, 01 Jun 2018 08:13:01 GMT
Repository: trafodion
Updated Branches:
  refs/heads/default [created] b68da51b0


Add Considerations for *CREATE INDEX Statement* in *Trafodion SQL Reference Manual* and Fix
Typos


Project: http://git-wip-us.apache.org/repos/asf/trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafodion/commit/76987d15
Tree: http://git-wip-us.apache.org/repos/asf/trafodion/tree/76987d15
Diff: http://git-wip-us.apache.org/repos/asf/trafodion/diff/76987d15

Branch: refs/heads/default
Commit: 76987d15200ef917714f6482be69b131ffd6a9f2
Parents: b04bfda
Author: liu.yu <qwertyioz@hotmail.com>
Authored: Tue May 29 18:22:51 2018 +0800
Committer: liu.yu <qwertyioz@hotmail.com>
Committed: Tue May 29 18:22:51 2018 +0800

----------------------------------------------------------------------
 .../src/asciidoc/_chapters/sql_statements.adoc  | 35 +++++++++++---------
 1 file changed, 20 insertions(+), 15 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafodion/blob/76987d15/docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc
----------------------------------------------------------------------
diff --git a/docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc b/docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc
index 26c2240..24aba0d 100644
--- a/docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc
+++ b/docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc
@@ -1850,6 +1850,11 @@ partitions are not audited and empty.
 If the operation fails after basic semantic checks are performed, the index no longer exists
and the entire transaction
 is rolled back even if it is a user-started transaction.
 
+If you are creating an index on a large Trafodion table that is already populated, 
+you should use the NO POPULATE option, and then run the POPULATE INDEX utility to load the
index. 
+Because CREATE INDEX executes in a single transaction, it could experience transactional
limitations such as a transaction timeout 
+if a large amount of data is to be moved.
+
 [[create_index_authorization_and_availability_requirements]]
 ==== Authorization and Availability Requirements
 
@@ -2069,13 +2074,13 @@ CREATE PROCEDURE procedure-ref([sql-parameter-list])
    EXTERNAL NAME 'java-method-name [java-signature]'
    LIBRARY [[catalog-name.]schema-name.]library-name
    [external security external-security-type]
-   language java
+   LANGUAGE java
    parameter style java
    [no sql | contains sql | modifies sql data | reads sql data]
    [dynamic result sets integer]
-   [transaction required | no transaction required]
-   [deterministic | not deterministic]
-   [no isolate | isolate]
+   [TRANSACTION REQUIRED | NO TRANSACTION REQUIRED]
+   [DETERMINISTIRC | NOT DETERMINISTRIC]
+   [NO ISOLATE| ISOLATE]
 
 procedure-ref is:
    [[catalog-name.]schema-name.]procedure-name
@@ -2259,7 +2264,7 @@ the database. However, be careful about the users to whom you grant
execute priv
 because those users will be able to execute the SPJ without requiring privileges to the underlying
database objects.
 
 <<<
-* `language java`
+* `LANGUAGE java`
 +
 specifies that the external user-defined routine is written in the java language.
 
@@ -2284,27 +2289,27 @@ contains a `java.sql.resultset[]` object. If the method contains a
result set ob
 The actual number of result sets returned by the SPJ method can be fewer than or equal to
this number. If you do not specify
 this option, then the default value is 0 (zero), meaning that the SPJ does not return result
sets.
 
-* `transaction required | no transaction required`
+* `TRANSACTION REQUIRED | NO TRANSACTION REQUIRED`
 +
-determines whether the SPJ must run in a transaction inherited from the calling application
(`transaction required`, the default
-option) or whether the SPJ runs without inheriting the calling application’s transaction
(`no transaction required`). Typically,
+determines whether the SPJ must run in a transaction inherited from the calling application
(`TRANSACTION REQUIRED`, the default
+option) or whether the SPJ runs without inheriting the calling application’s transaction
(`NO TRANSACTION REQUIRED`). Typically,
 you want the stored procedure to inherit the transaction from the calling application. However,
if the SPJ method does
 not access the database or if you want the stored procedure to manage its own transactions,
then you should set the stored
-procedure’s transaction attribute to no transaction required. For more information, see
+procedure’s transaction attribute to `NO TRANSACTION REQUIRED`. For more information, see
 <<effects_of_the_transaction_attribute_on_spjs,effects of the transaction attribute
on SPJs>>.
 
 <<<
-* `deterministic | not deterministic`
+* `DETERMINISTRIC | NOT DETERMINISTRIC`
 +
 specifies whether the SPJ always returns the same values for out and inout parameters for
a given set of argument values
-(`deterministic`) or does not return the same values (`not deterministic`, the default option).
If you specify `deterministic`,
+(`DETERMINISTRIC`) or does not return the same values (`NOT DETERMINISTRIC`, the default
option). If you specify `DETERMINISTRIC`,
 {project-name} is not required to call the SPJ each time to produce results; instead, {project-name}
caches the results and
 reuses them during subsequent calls, thus optimizing the CALL statement.
 
-* `no isolate | isolate`
+* `NO ISOLATE | ISOLATE`
 +
-specifies that the SPJ executes either in the environment of the database server (`no isolate`)
or in an isolated environment
-(`isolate`, the default option). {project-name} allows both options but always executes the
SPJ in the UDR server process (`isolate`).
+specifies that the SPJ executes either in the environment of the database server (`NO ISOLATE`)
or in an isolated environment
+(`ISOLATE`, the default option). {project-name} allows both options but always executes the
SPJ in the UDR server process (`ISOLATE`).
 
 [[create_procedure_considerations]]
 === Considerations for CREATE PROCEDURE
@@ -2669,7 +2674,7 @@ DB ROOT or anyone granted the DB_ROOTROLE role can grant the CREATE_SCHEMA
privi
 [[create_schema_examples]]
 === Examples of CREATE SCHEMA
 
-* This example creates a private schema schema named MYSCHEMA, which will be owned by the
current user:
+* This example creates a private schema named MYSCHEMA, which will be owned by the current
user:
 +
 ```
 CREATE SCHEMA myschema;


Mime
View raw message