http://git-wip-us.apache.org/repos/asf/incubator-trafodion-site/blob/11567d60/docs/2.0.0/sql_reference/index.html ---------------------------------------------------------------------- diff --git a/docs/2.0.0/sql_reference/index.html b/docs/2.0.0/sql_reference/index.html index aea4bfb..807c0d1 100644 --- a/docs/2.0.0/sql_reference/index.html +++ b/docs/2.0.0/sql_reference/index.html @@ -608,384 +608,377 @@ table.CodeRay td.code>pre{padding:0} <li><a href="#show_get_and_explain_statements">3.1.9. SHOW, GET, and EXPLAIN Statements</a></li> </ul> </li> -<li><a href="#alter_library_statement">3.2. ALTER LIBRARY Statement</a> +<li><a href="#alter_table_statement">3.2. ALTER TABLE Statement</a> <ul class="sectlevel3"> -<li><a href="#alter_library_syntax">3.2.1. Syntax Description of ALTER LIBRARY</a></li> -<li><a href="#alter_library_considerations">3.2.2. Considerations for ALTER LIBRARY</a></li> -<li><a href="#alter_library_examples">3.2.3. Examples of ALTER LIBRARY</a></li> +<li><a href="#alter_table_syntax">3.2.1. Syntax Description of ALTER TABLE</a></li> +<li><a href="#alter_table_considerations">3.2.2. Considerations for ALTER TABLE</a></li> +<li><a href="#alter_table_examples">3.2.3. Example of ALTER TABLE</a></li> </ul> </li> -<li><a href="#alter_table_statement">3.3. ALTER TABLE Statement</a> +<li><a href="#alter_user_statement">3.3. ALTER USER Statement</a> <ul class="sectlevel3"> -<li><a href="#alter_table_syntax">3.3.1. Syntax Description of ALTER TABLE</a></li> -<li><a href="#alter_table_considerations">3.3.2. Considerations for ALTER TABLE</a></li> -<li><a href="#alter_table_examples">3.3.3. Example of ALTER TABLE</a></li> +<li><a href="#alter_user_syntax">3.3.1. Syntax Description of ALTER USER</a></li> +<li><a href="#alter_user_considerations">3.3.2. Considerations for ALTER USER</a></li> +<li><a href="#alter_user_examples">3.3.3. Examples of ALTER USER</a></li> </ul> </li> -<li><a href="#alter_user_statement">3.4. ALTER USER Statement</a> +<li><a href="#begin_work_statement">3.4. BEGIN WORK Statement</a> <ul class="sectlevel3"> -<li><a href="#alter_user_syntax">3.4.1. Syntax Description of ALTER USER</a></li> -<li><a href="#alter_user_considerations">3.4.2. Considerations for ALTER USER</a></li> -<li><a href="#alter_user_examples">3.4.3. Examples of ALTER USER</a></li> +<li><a href="#begin_work_considerations">3.4.1. Considerations for BEGIN WORK</a></li> +<li><a href="#begin_work_examples">3.4.2. Example of BEGIN WORK</a></li> </ul> </li> -<li><a href="#begin_work_statement">3.5. BEGIN WORK Statement</a> +<li><a href="#call_statement">3.5. CALL Statement</a> <ul class="sectlevel3"> -<li><a href="#begin_work_considerations">3.5.1. Considerations for BEGIN WORK</a></li> -<li><a href="#begin_work_examples">3.5.2. Example of BEGIN WORK</a></li> +<li><a href="#call_syntax">3.5.1. Syntax Description of CALL</a></li> +<li><a href="#call_considerations">3.5.2. Considerations for CALL</a></li> +<li><a href="#call_examples">3.5.3. Examples of CALL</a></li> </ul> </li> -<li><a href="#call_statement">3.6. CALL Statement</a> +<li><a href="#commit_work_statement">3.6. COMMIT WORK Statement</a> <ul class="sectlevel3"> -<li><a href="#call_syntax">3.6.1. Syntax Description of CALL</a></li> -<li><a href="#call_considerations">3.6.2. Considerations for CALL</a></li> -<li><a href="#call_examples">3.6.3. Examples of CALL</a></li> +<li><a href="#commit_work_considerations">3.6.1. Considerations for COMMIT WORK</a></li> +<li><a href="#commit_work_examples">3.6.2. Example of COMMIT WORK</a></li> </ul> </li> -<li><a href="#commit_work_statement">3.7. COMMIT WORK Statement</a> +<li><a href="#control_query_cancel_statement">3.7. CONTROL QUERY CANCEL Statement</a> <ul class="sectlevel3"> -<li><a href="#commit_work_considerations">3.7.1. Considerations for COMMIT WORK</a></li> -<li><a href="#commit_work_examples">3.7.2. Example of COMMIT WORK</a></li> +<li><a href="#control_query_cancel_syntax">3.7.1. Syntax Description of CONTROL QUERY CANCEL</a></li> +<li><a href="#control_query_cancel_considerations">3.7.2. Considerations for CONTROL QUERY CANCEL</a></li> +<li><a href="#control_query_cancel_examples">3.7.3. Example of CONTROL QUERY CANCEL</a></li> </ul> </li> -<li><a href="#control_query_cancel_statement">3.8. CONTROL QUERY CANCEL Statement</a> +<li><a href="#control_query_default_statement">3.8. CONTROL QUERY DEFAULT Statement</a> <ul class="sectlevel3"> -<li><a href="#control_query_cancel_syntax">3.8.1. Syntax Description of CONTROL QUERY CANCEL</a></li> -<li><a href="#control_query_cancel_considerations">3.8.2. Considerations for CONTROL QUERY CANCEL</a></li> -<li><a href="#control_query_cancel_examples">3.8.3. Example of CONTROL QUERY CANCEL</a></li> +<li><a href="#control_query_default_syntax">3.8.1. Syntax Description of CONTROL QUERY DEFAULT</a></li> +<li><a href="#control_query_default_considerations">3.8.2. Considerations for CONTROL QUERY DEFAULT</a></li> +<li><a href="#control_query_default_examples">3.8.3. Examples of CONTROL QUERY DEFAULT</a></li> </ul> </li> -<li><a href="#control_query_default_statement">3.9. CONTROL QUERY DEFAULT Statement</a> +<li><a href="#create_function_statement">3.9. CREATE FUNCTION Statement</a> <ul class="sectlevel3"> -<li><a href="#control_query_default_syntax">3.9.1. Syntax Description of CONTROL QUERY DEFAULT</a></li> -<li><a href="#control_query_default_considerations">3.9.2. Considerations for CONTROL QUERY DEFAULT</a></li> -<li><a href="#control_query_default_examples">3.9.3. Examples of CONTROL QUERY DEFAULT</a></li> +<li><a href="#create_function_syntax">3.9.1. Syntax Description of CREATE FUNCTION</a></li> +<li><a href="#create_function_considerations">3.9.2. Considerations for CREATE FUNCTION</a></li> +<li><a href="#create_function_examples">3.9.3. Examples of CREATE FUNCTION</a></li> </ul> </li> -<li><a href="#create_function_statement">3.10. CREATE FUNCTION Statement</a> +<li><a href="#create_index_statement">3.10. CREATE INDEX Statement</a> <ul class="sectlevel3"> -<li><a href="#create_function_syntax">3.10.1. Syntax Description of CREATE FUNCTION</a></li> -<li><a href="#create_function_considerations">3.10.2. Considerations for CREATE FUNCTION</a></li> -<li><a href="#create_function_examples">3.10.3. Examples of CREATE FUNCTION</a></li> +<li><a href="#create_index_syntax">3.10.1. Syntax Description of CREATE INDEX</a></li> +<li><a href="#create_index_considerations">3.10.2. Considerations for CREATE INDEX</a></li> +<li><a href="#create_index_examples">3.10.3. Examples of CREATE INDEX</a></li> </ul> </li> -<li><a href="#create_index_statement">3.11. CREATE INDEX Statement</a> +<li><a href="#create_library_statement">3.11. CREATE LIBRARY Statement</a> <ul class="sectlevel3"> -<li><a href="#create_index_syntax">3.11.1. Syntax Description of CREATE INDEX</a></li> -<li><a href="#create_index_considerations">3.11.2. Considerations for CREATE INDEX</a></li> -<li><a href="#create_index_examples">3.11.3. Examples of CREATE INDEX</a></li> +<li><a href="#create_library_syntax">3.11.1. Syntax Description of CREATE LIBRARY</a></li> +<li><a href="#create_library_considerations">3.11.2. Considerations for CREATE LIBRARY</a></li> +<li><a href="#create_library_examples">3.11.3. Examples of CREATE LIBRARY</a></li> </ul> </li> -<li><a href="#create_library_statement">3.12. CREATE LIBRARY Statement</a> +<li><a href="#create_procedure_statement">3.12. CREATE PROCEDURE Statement</a> <ul class="sectlevel3"> -<li><a href="#create_library_syntax">3.12.1. Syntax Description of CREATE LIBRARY</a></li> -<li><a href="#create_library_considerations">3.12.2. Considerations for CREATE LIBRARY</a></li> -<li><a href="#create_library_examples">3.12.3. Examples of CREATE LIBRARY</a></li> +<li><a href="#create_procedure_syntax">3.12.1. Syntax Description of CREATE PROCEDURE</a></li> +<li><a href="#create_procedure_considerations">3.12.2. Considerations for CREATE PROCEDURE</a></li> +<li><a href="#create_procedure_examples">3.12.3. Examples of CREATE PROCEDURE</a></li> </ul> </li> -<li><a href="#create_procedure_statement">3.13. CREATE PROCEDURE Statement</a> +<li><a href="#create_role_statement">3.13. CREATE ROLE Statement</a> <ul class="sectlevel3"> -<li><a href="#create_procedure_syntax">3.13.1. Syntax Description of CREATE PROCEDURE</a></li> -<li><a href="#create_procedure_considerations">3.13.2. Considerations for CREATE PROCEDURE</a></li> -<li><a href="#create_procedure_examples">3.13.3. Examples of CREATE PROCEDURE</a></li> +<li><a href="#create_role_syntax">3.13.1. Syntax Description of CREATE ROLE</a></li> +<li><a href="#create_role_considerations">3.13.2. Considerations for CREATE ROLE</a></li> +<li><a href="#create_role_examples">3.13.3. Examples of CREATE ROLE</a></li> </ul> </li> -<li><a href="#create_role_statement">3.14. CREATE ROLE Statement</a> +<li><a href="#create_schema_statement">3.14. CREATE SCHEMA Statement</a> <ul class="sectlevel3"> -<li><a href="#create_role_syntax">3.14.1. Syntax Description of CREATE ROLE</a></li> -<li><a href="#create_role_considerations">3.14.2. Considerations for CREATE ROLE</a></li> -<li><a href="#create_role_examples">3.14.3. Examples of CREATE ROLE</a></li> +<li><a href="#create_schema_syntax">3.14.1. Syntax Description of CREATE SCHEMA</a></li> +<li><a href="#create_schema_considerations">3.14.2. Considerations for CREATE SCHEMA</a></li> +<li><a href="#create_schema_examples">3.14.3. Examples of CREATE SCHEMA</a></li> </ul> </li> -<li><a href="#create_schema_statement">3.15. CREATE SCHEMA Statement</a> +<li><a href="#create_table_statement">3.15. CREATE TABLE Statement</a> <ul class="sectlevel3"> -<li><a href="#create_schema_syntax">3.15.1. Syntax Description of CREATE SCHEMA</a></li> -<li><a href="#create_schema_considerations">3.15.2. Considerations for CREATE SCHEMA</a></li> -<li><a href="#create_schema_examples">3.15.3. Examples of CREATE SCHEMA</a></li> +<li><a href="#create_table_syntax">3.15.1. Syntax Description of CREATE TABLE</a></li> +<li><a href="#create_table_considerations">3.15.2. Considerations for CREATE TABLE</a></li> +<li><a href="#create_table_trafodion_sql_extensions_to_create_table">3.15.3. Trafodion SQL Extensions to CREATE TABLE</a></li> +<li><a href="#create_table_examples">3.15.4. Examples of CREATE TABLE</a></li> </ul> </li> -<li><a href="#create_table_statement">3.16. CREATE TABLE Statement</a> +<li><a href="#create_view_statement">3.16. CREATE VIEW Statement</a> <ul class="sectlevel3"> -<li><a href="#create_table_syntax">3.16.1. Syntax Description of CREATE TABLE</a></li> -<li><a href="#create_table_considerations">3.16.2. Considerations for CREATE TABLE</a></li> -<li><a href="#create_table_trafodion_sql_extensions_to_create_table">3.16.3. Trafodion SQL Extensions to CREATE TABLE</a></li> -<li><a href="#create_table_examples">3.16.4. Examples of CREATE TABLE</a></li> +<li><a href="#create_view_syntax">3.16.1. Syntax Description of CREATE VIEW</a></li> +<li><a href="#create_view_considerations">3.16.2. Considerations for CREATE VIEW</a></li> +<li><a href="#create_view_examples">3.16.3. Examples of CREATE VIEW</a></li> </ul> </li> -<li><a href="#create_view_statement">3.17. CREATE VIEW Statement</a> +<li><a href="#delete_statement">3.17. DELETE Statement</a> <ul class="sectlevel3"> -<li><a href="#create_view_syntax">3.17.1. Syntax Description of CREATE VIEW</a></li> -<li><a href="#create_view_considerations">3.17.2. Considerations for CREATE VIEW</a></li> -<li><a href="#create_view_examples">3.17.3. Examples of CREATE VIEW</a></li> +<li><a href="#delete_syntax">3.17.1. Syntax Description of DELETE</a></li> +<li><a href="#delete_considerations">3.17.2. Considerations for DELETE</a></li> +<li><a href="#delete_examples">3.17.3. Examples of DELETE</a></li> </ul> </li> -<li><a href="#delete_statement">3.18. DELETE Statement</a> +<li><a href="#drop_function_statement">3.18. DROP FUNCTION Statement</a> <ul class="sectlevel3"> -<li><a href="#delete_syntax">3.18.1. Syntax Description of DELETE</a></li> -<li><a href="#delete_considerations">3.18.2. Considerations for DELETE</a></li> -<li><a href="#delete_examples">3.18.3. Examples of DELETE</a></li> +<li><a href="#drop_function_syntax">3.18.1. Syntax Description of DROP FUNCTION</a></li> +<li><a href="#drop_function_considerations">3.18.2. Considerations for DROP FUNCTION</a></li> +<li><a href="#drop_function_examples">3.18.3. Examples of DROP FUNCTION</a></li> </ul> </li> -<li><a href="#drop_function_statement">3.19. DROP FUNCTION Statement</a> +<li><a href="#drop_index_statement">3.19. DROP INDEX Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_function_syntax">3.19.1. Syntax Description of DROP FUNCTION</a></li> -<li><a href="#drop_function_considerations">3.19.2. Considerations for DROP FUNCTION</a></li> -<li><a href="#drop_function_examples">3.19.3. Examples of DROP FUNCTION</a></li> +<li><a href="#drop_index_syntax">3.19.1. Syntax Description of DROP INDEX</a></li> +<li><a href="#drop_index_considerations">3.19.2. Considerations for DROP INDEX</a></li> +<li><a href="#drop_index_examples">3.19.3. Examples of DROP INDEX</a></li> </ul> </li> -<li><a href="#drop_index_statement">3.20. DROP INDEX Statement</a> +<li><a href="#drop_library_statement">3.20. DROP LIBRARY Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_index_syntax">3.20.1. Syntax Description of DROP INDEX</a></li> -<li><a href="#drop_index_considerations">3.20.2. Considerations for DROP INDEX</a></li> -<li><a href="#drop_index_examples">3.20.3. Examples of DROP INDEX</a></li> +<li><a href="#drop_library_syntax">3.20.1. Syntax Description of DROP LIBRARY</a></li> +<li><a href="#drop_library_considerations">3.20.2. Considerations for DROP LIBRARY</a></li> +<li><a href="#drop_library_examples">3.20.3. Examples of DROP LIBRARY</a></li> </ul> </li> -<li><a href="#drop_library_statement">3.21. DROP LIBRARY Statement</a> +<li><a href="#drop_procedure_statement">3.21. DROP PROCEDURE Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_library_syntax">3.21.1. Syntax Description of DROP LIBRARY</a></li> -<li><a href="#drop_library_considerations">3.21.2. Considerations for DROP LIBRARY</a></li> -<li><a href="#drop_library_examples">3.21.3. Examples of DROP LIBRARY</a></li> +<li><a href="#drop_procedure_syntax">3.21.1. Syntax Description of DROP PROCEDURE</a></li> +<li><a href="#drop_procedure_considerations">3.21.2. Considerations for DROP PROCEDURE</a></li> +<li><a href="#drop_procedure_examples">3.21.3. Examples of DROP PROCEDURE</a></li> </ul> </li> -<li><a href="#drop_procedure_statement">3.22. DROP PROCEDURE Statement</a> +<li><a href="#drop_role_statement">3.22. DROP ROLE Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_procedure_syntax">3.22.1. Syntax Description of DROP PROCEDURE</a></li> -<li><a href="#drop_procedure_considerations">3.22.2. Considerations for DROP PROCEDURE</a></li> -<li><a href="#drop_procedure_examples">3.22.3. Examples of DROP PROCEDURE</a></li> +<li><a href="#drop_role_syntax">3.22.1. Syntax Description of DROP ROLE</a></li> +<li><a href="#drop_role_considerations">3.22.2. Considerations for DROP ROLE</a></li> +<li><a href="#drop_role_examples">3.22.3. Examples of DROP ROLE</a></li> </ul> </li> -<li><a href="#drop_role_statement">3.23. DROP ROLE Statement</a> +<li><a href="#drop_schema_statement">3.23. DROP SCHEMA Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_role_syntax">3.23.1. Syntax Description of DROP ROLE</a></li> -<li><a href="#drop_role_considerations">3.23.2. Considerations for DROP ROLE</a></li> -<li><a href="#drop_role_examples">3.23.3. Examples of DROP ROLE</a></li> +<li><a href="#drop_schema_syntax">3.23.1. Syntax Description of DROP SCHEMA</a></li> +<li><a href="#drop_schema_considerations">3.23.2. Considerations for DROP SCHEMA</a></li> +<li><a href="#drop_schema_examples">3.23.3. Example of DROP SCHEMA</a></li> </ul> </li> -<li><a href="#drop_schema_statement">3.24. DROP SCHEMA Statement</a> +<li><a href="#drop_table_statement">3.24. DROP TABLE Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_schema_syntax">3.24.1. Syntax Description of DROP SCHEMA</a></li> -<li><a href="#drop_schema_considerations">3.24.2. Considerations for DROP SCHEMA</a></li> -<li><a href="#drop_schema_examples">3.24.3. Example of DROP SCHEMA</a></li> +<li><a href="#drop_table_syntax">3.24.1. Syntax Description of DROP TABLE</a></li> +<li><a href="#drop_table_considerations">3.24.2. Considerations for DROP TABLE</a></li> +<li><a href="#drop_table_examples">3.24.3. Examples of DROP TABLE</a></li> </ul> </li> -<li><a href="#drop_table_statement">3.25. DROP TABLE Statement</a> +<li><a href="#drop_view_statement">3.25. DROP VIEW Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_table_syntax">3.25.1. Syntax Description of DROP TABLE</a></li> -<li><a href="#drop_table_considerations">3.25.2. Considerations for DROP TABLE</a></li> -<li><a href="#drop_table_examples">3.25.3. Examples of DROP TABLE</a></li> +<li><a href="#drop_view_syntax">3.25.1. Syntax Description of DROP VIEW</a></li> +<li><a href="#drop_view_considerations">3.25.2. Considerations for DROP VIEW</a></li> +<li><a href="#drop_view_examples">3.25.3. Example of DROP VIEW</a></li> </ul> </li> -<li><a href="#drop_view_statement">3.26. DROP VIEW Statement</a> +<li><a href="#execute_statement">3.26. Execute Statement</a> <ul class="sectlevel3"> -<li><a href="#drop_view_syntax">3.26.1. Syntax Description of DROP VIEW</a></li> -<li><a href="#drop_view_considerations">3.26.2. Considerations for DROP VIEW</a></li> -<li><a href="#drop_view_examples">3.26.3. Example of DROP VIEW</a></li> +<li><a href="#execute_syntax">3.26.1. Syntax Description of EXECUTE</a></li> +<li><a href="#execute_considerations">3.26.2. Considerations for EXECUTE</a></li> +<li><a href="#execute_examples">3.26.3. Examples of EXECUTE</a></li> </ul> </li> -<li><a href="#execute_statement">3.27. Execute Statement</a> +<li><a href="#explain_statement">3.27. EXPLAIN Statement</a> <ul class="sectlevel3"> -<li><a href="#execute_syntax">3.27.1. Syntax Description of EXECUTE</a></li> -<li><a href="#execute_considerations">3.27.2. Considerations for EXECUTE</a></li> -<li><a href="#execute_examples">3.27.3. Examples of EXECUTE</a></li> +<li><a href="#explain_syntax">3.27.1. Syntax Description of EXPLAIN</a></li> +<li><a href="#explain_considerations">3.27.2. Considerations for EXPLAIN</a></li> </ul> </li> -<li><a href="#explain_statement">3.28. EXPLAIN Statement</a> +<li><a href="#get_statement">3.28. GET Statement</a> <ul class="sectlevel3"> -<li><a href="#explain_syntax">3.28.1. Syntax Description of EXPLAIN</a></li> -<li><a href="#explain_considerations">3.28.2. Considerations for EXPLAIN</a></li> +<li><a href="#get_syntax">3.28.1. Syntax Description of GET</a></li> +<li><a href="#get_considerations">3.28.2. Considerations for GET</a></li> +<li><a href="#get_examples">3.28.3. Examples of GET</a></li> </ul> </li> -<li><a href="#get_statement">3.29. GET Statement</a> +<li><a href="#get_hbase_objects_statement">3.29. GET HBASE OBJECTS Statement</a> <ul class="sectlevel3"> -<li><a href="#get_syntax">3.29.1. Syntax Description of GET</a></li> -<li><a href="#get_considerations">3.29.2. Considerations for GET</a></li> -<li><a href="#get_examples">3.29.3. Examples of GET</a></li> +<li><a href="#get_hbase_objects_syntax">3.29.1. Syntax Description of GET HBASE OBJECTS</a></li> +<li><a href="#get_hbase_objects_examples">3.29.2. Examples of GET HBASE OBJECTS</a></li> </ul> </li> -<li><a href="#get_hbase_objects_statement">3.30. GET HBASE OBJECTS Statement</a> +<li><a href="#get_version_of_metadata_statement">3.30. GET VERSION OF METADATA Statement</a> <ul class="sectlevel3"> -<li><a href="#get_hbase_objects_syntax">3.30.1. Syntax Description of GET HBASE OBJECTS</a></li> -<li><a href="#get_hbase_objects_examples">3.30.2. Examples of GET HBASE OBJECTS</a></li> +<li><a href="#get_version_of_metadata_considerations">3.30.1. Considerations for GET VERSION OF METADATA</a></li> +<li><a href="#get_version_of_metadata_examples">3.30.2. Examples of GET VERSION OF METADATA</a></li> </ul> </li> -<li><a href="#get_version_of_metadata_statement">3.31. GET VERSION OF METADATA Statement</a> +<li><a href="#get_version_of_software_statement">3.31. GET VERSION OF SOFTWARE Statement</a> <ul class="sectlevel3"> -<li><a href="#get_version_of_metadata_considerations">3.31.1. Considerations for GET VERSION OF METADATA</a></li> -<li><a href="#get_version_of_metadata_examples">3.31.2. Examples of GET VERSION OF METADATA</a></li> +<li><a href="#get_version_of_software_considerations">3.31.1. Considerations for GET VERSION OF SOFTWARE</a></li> +<li><a href="#get_version_of_software_examples">3.31.2. Examples of GET VERSION OF SOFTWARE</a></li> </ul> </li> -<li><a href="#get_version_of_software_statement">3.32. GET VERSION OF SOFTWARE Statement</a> +<li><a href="#grant_statement">3.32. GRANT Statement</a> <ul class="sectlevel3"> -<li><a href="#get_version_of_software_considerations">3.32.1. Considerations for GET VERSION OF SOFTWARE</a></li> -<li><a href="#get_version_of_software_examples">3.32.2. Examples of GET VERSION OF SOFTWARE</a></li> +<li><a href="#_syntax_description_of_grant">3.32.1. syntax description of grant</a></li> +<li><a href="#grant_considerations">3.32.2. Considerations for GRANT</a></li> +<li><a href="#grant_examples">3.32.3. Examples of GRANT</a></li> </ul> </li> -<li><a href="#grant_statement">3.33. GRANT Statement</a> +<li><a href="#grant_component_privilege_statement">3.33. GRANT COMPONENT PRIVILEGE Statement</a> <ul class="sectlevel3"> -<li><a href="#_syntax_description_of_grant">3.33.1. syntax description of grant</a></li> -<li><a href="#grant_considerations">3.33.2. Considerations for GRANT</a></li> -<li><a href="#grant_examples">3.33.3. Examples of GRANT</a></li> +<li><a href="#grant_component_privilege_syntax">3.33.1. Syntax Description of GRANT COMPONENT PRIVILEGE</a></li> +<li><a href="#grant_component_privilege_considerations">3.33.2. Considerations for GRANT COMPONENT PRIVILEGE</a></li> +<li><a href="#grant_component_privilege_considerations">3.33.3. Examples of GRANT COMPONENT PRIVILEGE</a></li> </ul> </li> -<li><a href="#grant_component_privilege_statement">3.34. GRANT COMPONENT PRIVILEGE Statement</a> +<li><a href="#grant_role_statement">3.34. GRANT ROLE Statement</a> <ul class="sectlevel3"> -<li><a href="#grant_component_privilege_syntax">3.34.1. Syntax Description of GRANT COMPONENT PRIVILEGE</a></li> -<li><a href="#grant_component_privilege_considerations">3.34.2. Considerations for GRANT COMPONENT PRIVILEGE</a></li> -<li><a href="#grant_component_privilege_considerations">3.34.3. Examples of GRANT COMPONENT PRIVILEGE</a></li> +<li><a href="#grant_role_syntax">3.34.1. Syntax Description of GRANT ROLE</a></li> +<li><a href="#grant_role_considerations">3.34.2. Considerations for GRANT ROLE</a></li> +<li><a href="#grant_role_examples">3.34.3. Examples of GRANT ROLE</a></li> </ul> </li> -<li><a href="#grant_role_statement">3.35. GRANT ROLE Statement</a> +<li><a href="#insert_statement">3.35. INSERT Statement</a> <ul class="sectlevel3"> -<li><a href="#grant_role_syntax">3.35.1. Syntax Description of GRANT ROLE</a></li> -<li><a href="#grant_role_considerations">3.35.2. Considerations for GRANT ROLE</a></li> -<li><a href="#grant_role_examples">3.35.3. Examples of GRANT ROLE</a></li> +<li><a href="#insert_syntax">3.35.1. Syntax Description of INSERT</a></li> +<li><a href="#insert_considerations">3.35.2. Considerations for INSERT</a></li> +<li><a href="#insert_examples">3.35.3. Examples of INSERT</a></li> </ul> </li> -<li><a href="#insert_statement">3.36. INSERT Statement</a> +<li><a href="#invoke_statement">3.36. INVOKE Statement</a> <ul class="sectlevel3"> -<li><a href="#insert_syntax">3.36.1. Syntax Description of INSERT</a></li> -<li><a href="#insert_considerations">3.36.2. Considerations for INSERT</a></li> -<li><a href="#insert_examples">3.36.3. Examples of INSERT</a></li> +<li><a href="#invoke_syntax">3.36.1. Syntax Description of INVOKE</a></li> +<li><a href="#invoke_considerations">3.36.2. Considerations for INVOKE</a></li> +<li><a href="#invoke_required_privileges">3.36.3. Required Privileges</a></li> +<li><a href="#invoke_examples">3.36.4. Examples of INVOKE</a></li> </ul> </li> -<li><a href="#invoke_statement">3.37. INVOKE Statement</a> +<li><a href="#merge_statement">3.37. MERGE Statement</a> <ul class="sectlevel3"> -<li><a href="#invoke_syntax">3.37.1. Syntax Description of INVOKE</a></li> -<li><a href="#invoke_considerations">3.37.2. Considerations for INVOKE</a></li> -<li><a href="#invoke_required_privileges">3.37.3. Required Privileges</a></li> -<li><a href="#invoke_examples">3.37.4. Examples of INVOKE</a></li> +<li><a href="#merge_syntax">3.37.1. Syntax Description of MERGE</a></li> +<li><a href="#merge_considerations">3.37.2. Considerations for MERGE</a></li> +<li><a href="#merge_upsert_using_single_row">3.37.3. Upsert Using Single Row</a></li> +<li><a href="#merge_examples">3.37.4. Examples of MERGE</a></li> </ul> </li> -<li><a href="#merge_statement">3.38. MERGE Statement</a> +<li><a href="#prepare_statement">3.38. PREPARE Statement</a> <ul class="sectlevel3"> -<li><a href="#merge_syntax">3.38.1. Syntax Description of MERGE</a></li> -<li><a href="#merge_considerations">3.38.2. Considerations for MERGE</a></li> -<li><a href="#merge_upsert_using_single_row">3.38.3. Upsert Using Single Row</a></li> -<li><a href="#merge_examples">3.38.4. Examples of MERGE</a></li> +<li><a href="#prepare_syntax">3.38.1. Syntax Description of PREPARE</a></li> +<li><a href="#prepare_considerations">3.38.2. Considerations for PREPARE</a></li> +<li><a href="#prepare_examples">3.38.3. Examples of PREPARE</a></li> </ul> </li> -<li><a href="#prepare_statement">3.39. PREPARE Statement</a> +<li><a href="#register_user_statement">3.39. REGISTER USER Statement</a> <ul class="sectlevel3"> -<li><a href="#prepare_syntax">3.39.1. Syntax Description of PREPARE</a></li> -<li><a href="#prepare_considerations">3.39.2. Considerations for PREPARE</a></li> -<li><a href="#prepare_examples">3.39.3. Examples of PREPARE</a></li> +<li><a href="#register_user_syntax">3.39.1. Syntax Description of REGISTER USER</a></li> +<li><a href="#register_user_register_user_considerations">3.39.2. Considerations for REGISTER USER</a></li> +<li><a href="#register_user_examples">3.39.3. Examples of REGISTER USER</a></li> </ul> </li> -<li><a href="#register_user_statement">3.40. REGISTER USER Statement</a> +<li><a href="#_revoke_statement">3.40. REVOKE Statement</a> <ul class="sectlevel3"> -<li><a href="#register_user_syntax">3.40.1. Syntax Description of REGISTER USER</a></li> -<li><a href="#register_user_register_user_considerations">3.40.2. Considerations for REGISTER USER</a></li> -<li><a href="#register_user_examples">3.40.3. Examples of REGISTER USER</a></li> +<li><a href="#_syntax_description_of_revoke">3.40.1. Syntax Description of REVOKE</a></li> +<li><a href="#revoke_considerations">3.40.2. Considerations for REVOKE</a></li> +<li><a href="#revoke_examples">3.40.3. Examples of REVOKE</a></li> </ul> </li> -<li><a href="#_revoke_statement">3.41. REVOKE Statement</a> +<li><a href="#revoke_component_privilege_statement">3.41. REVOKE COMPONENT PRIVILEGE Statement</a> <ul class="sectlevel3"> -<li><a href="#_syntax_description_of_revoke">3.41.1. Syntax Description of REVOKE</a></li> -<li><a href="#revoke_considerations">3.41.2. Considerations for REVOKE</a></li> -<li><a href="#revoke_examples">3.41.3. Examples of REVOKE</a></li> +<li><a href="#_syntax_description_of_revoke_component_privilege">3.41.1. Syntax Description of REVOKE COMPONENT PRIVILEGE</a></li> +<li><a href="#revoke_component_privilege_considerations">3.41.2. Considerations for REVOKE COMPONENT PRIVILEGE</a></li> +<li><a href="#revoke_component_examples">3.41.3. Examples of REVOKE COMPONENT PRIVILEGE</a></li> </ul> </li> -<li><a href="#revoke_component_privilege_statement">3.42. REVOKE COMPONENT PRIVILEGE Statement</a> +<li><a href="#revoke_role_statement">3.42. REVOKE ROLE Statement</a> <ul class="sectlevel3"> -<li><a href="#_syntax_description_of_revoke_component_privilege">3.42.1. Syntax Description of REVOKE COMPONENT PRIVILEGE</a></li> -<li><a href="#revoke_component_privilege_considerations">3.42.2. Considerations for REVOKE COMPONENT PRIVILEGE</a></li> -<li><a href="#revoke_component_examples">3.42.3. Examples of REVOKE COMPONENT PRIVILEGE</a></li> +<li><a href="#revoke_role_syntax">3.42.1. Syntax Description of REVOKE ROLE</a></li> +<li><a href="#revoke_role_considerations">3.42.2. Considerations for REVOKE ROLE</a></li> +<li><a href="#revoke_role_examples">3.42.3. Examples of REVOKE ROLE</a></li> </ul> </li> -<li><a href="#revoke_role_statement">3.43. REVOKE ROLE Statement</a> +<li><a href="#rollback_work_statement">3.43. ROLLBACK WORK Statement</a> <ul class="sectlevel3"> -<li><a href="#revoke_role_syntax">3.43.1. Syntax Description of REVOKE ROLE</a></li> -<li><a href="#revoke_role_considerations">3.43.2. Considerations for REVOKE ROLE</a></li> -<li><a href="#revoke_role_examples">3.43.3. Examples of REVOKE ROLE</a></li> +<li><a href="#rollback_work_syntax">3.43.1. Syntax Description of ROLLBACK WORK</a></li> +<li><a href="#rollback_work_considerations">3.43.2. Considerations for ROLLBACK WORK</a></li> +<li><a href="#rollback_work_examples">3.43.3. Example of ROLLBACK WORK</a></li> </ul> </li> -<li><a href="#rollback_work_statement">3.44. ROLLBACK WORK Statement</a> +<li><a href="#select_statement">3.44. SELECT Statement</a> <ul class="sectlevel3"> -<li><a href="#rollback_work_syntax">3.44.1. Syntax Description of ROLLBACK WORK</a></li> -<li><a href="#rollback_work_considerations">3.44.2. Considerations for ROLLBACK WORK</a></li> -<li><a href="#rollback_work_examples">3.44.3. Example of ROLLBACK WORK</a></li> +<li><a href="#select_syntax">3.44.1. Syntax Description of SELECT</a></li> +<li><a href="#select_considerations">3.44.2. Considerations for SELECT</a></li> +<li><a href="#select_examples">3.44.3. Examples of SELECT</a></li> </ul> </li> -<li><a href="#select_statement">3.45. SELECT Statement</a> +<li><a href="#set_schema_statement">3.45. SET SCHEMA Statement</a> <ul class="sectlevel3"> -<li><a href="#select_syntax">3.45.1. Syntax Description of SELECT</a></li> -<li><a href="#select_considerations">3.45.2. Considerations for SELECT</a></li> -<li><a href="#select_examples">3.45.3. Examples of SELECT</a></li> +<li><a href="#set_schema_syntax">3.45.1. Syntax Description of SET SCHEMA</a></li> +<li><a href="#set_schema_considerations">3.45.2. Considerations for SET SCHEMA</a></li> +<li><a href="#set_schema_examples">3.45.3. Examples of SET SCHEMA</a></li> </ul> </li> -<li><a href="#set_schema_statement">3.46. SET SCHEMA Statement</a> +<li><a href="#set_transaction_statement">3.46. SET TRANSACTION Statement</a> <ul class="sectlevel3"> -<li><a href="#set_schema_syntax">3.46.1. Syntax Description of SET SCHEMA</a></li> -<li><a href="#set_schema_considerations">3.46.2. Considerations for SET SCHEMA</a></li> -<li><a href="#set_schema_examples">3.46.3. Examples of SET SCHEMA</a></li> +<li><a href="#set_transaction_syntax">3.46.1. Syntax Description of SET TRANSACTION</a></li> +<li><a href="#set_transaction_consideration">3.46.2. Considerations for SET TRANSACTION</a></li> +<li><a href="#set_transaction_examples">3.46.3. Examples of SET TRANSACTION</a></li> </ul> </li> -<li><a href="#set_transaction_statement">3.47. SET TRANSACTION Statement</a> +<li><a href="#showcontrol_statement">3.47. SHOWCONTROL Statement</a> <ul class="sectlevel3"> -<li><a href="#set_transaction_syntax">3.47.1. Syntax Description of SET TRANSACTION</a></li> -<li><a href="#set_transaction_consideration">3.47.2. Considerations for SET TRANSACTION</a></li> -<li><a href="#set_transaction_examples">3.47.3. Examples of SET TRANSACTION</a></li> +<li><a href="#showcontrol_syntax">3.47.1. Syntax Description of SHOWCONTROL</a></li> +<li><a href="#showcontrol_examples">3.47.2. Examples of SHOWCONTROL</a></li> </ul> </li> -<li><a href="#showcontrol_statement">3.48. SHOWCONTROL Statement</a> +<li><a href="#showddl_statement">3.48. SHOWDDL Statement</a> <ul class="sectlevel3"> -<li><a href="#showcontrol_syntax">3.48.1. Syntax Description of SHOWCONTROL</a></li> -<li><a href="#showcontrol_examples">3.48.2. Examples of SHOWCONTROL</a></li> +<li><a href="#showddl_syntax">3.48.1. Syntax Description of SHOWDDL</a></li> +<li><a href="#showddl_considerations">3.48.2. Considerations for SHOWDDL</a></li> +<li><a href="#showddl_examples">3.48.3. Examples of SHOWDDL</a></li> </ul> </li> -<li><a href="#showddl_statement">3.49. SHOWDDL Statement</a> +<li><a href="#showddl_schema_statement">3.49. SHOWDDL SCHEMA Statement</a> <ul class="sectlevel3"> -<li><a href="#showddl_syntax">3.49.1. Syntax Description of SHOWDDL</a></li> -<li><a href="#showddl_considerations">3.49.2. Considerations for SHOWDDL</a></li> -<li><a href="#showddl_examples">3.49.3. Examples of SHOWDDL</a></li> +<li><a href="#showddl_schema_syntax">3.49.1. Syntax Description for SHOWDDL SCHEMA</a></li> +<li><a href="#showddl_schema_considerations">3.49.2. Considerations for SHOWDDL SCHEMA</a></li> +<li><a href="#showddl_schema_examples">3.49.3. Examples of SHOWDDL SCHEMA</a></li> </ul> </li> -<li><a href="#showddl_schema_statement">3.50. SHOWDDL SCHEMA Statement</a> +<li><a href="#_showstats_statement">3.50. SHOWSTATS Statement</a> <ul class="sectlevel3"> -<li><a href="#showddl_schema_syntax">3.50.1. Syntax Description for SHOWDDL SCHEMA</a></li> -<li><a href="#showddl_schema_considerations">3.50.2. Considerations for SHOWDDL SCHEMA</a></li> -<li><a href="#showddl_schema_examples">3.50.3. Examples of SHOWDDL SCHEMA</a></li> +<li><a href="#showstats_syntax">3.50.1. Syntax Description of SHOWSTATS</a></li> +<li><a href="#showstats_considerations">3.50.2. Considerations for SHOWSTATS</a></li> +<li><a href="#showstats_examples">3.50.3. Examples of SHOWSTATS</a></li> </ul> </li> -<li><a href="#_showstats_statement">3.51. SHOWSTATS Statement</a> +<li><a href="#table_statement">3.51. TABLE Statement</a> <ul class="sectlevel3"> -<li><a href="#showstats_syntax">3.51.1. Syntax Description of SHOWSTATS</a></li> -<li><a href="#showstats_considerations">3.51.2. Considerations for SHOWSTATS</a></li> -<li><a href="#showstats_examples">3.51.3. Examples of SHOWSTATS</a></li> +<li><a href="#table_syntax">3.51.1. Syntax Description of Table Statement</a></li> +<li><a href="#_considerations_for_table">3.51.2. Considerations for TABLE</a></li> +<li><a href="#_examples_of_table_statement">3.51.3. Examples of TABLE Statement</a></li> </ul> </li> -<li><a href="#table_statement">3.52. TABLE Statement</a> +<li><a href="#unregister_user_statement">3.52. UNREGISTER USER Statement</a> <ul class="sectlevel3"> -<li><a href="#table_syntax">3.52.1. Syntax Description of Table Statement</a></li> -<li><a href="#_considerations_for_table">3.52.2. Considerations for TABLE</a></li> -<li><a href="#_examples_of_table_statement">3.52.3. Examples of TABLE Statement</a></li> +<li><a href="#unregister_user_syntax">3.52.1. Syntax Description of UNREGISTER USER</a></li> +<li><a href="#unregister_user_considerations">3.52.2. Considerations for UNREGISTER USER</a></li> +<li><a href="#unregister_user_examples">3.52.3. Examples of UNREGISTER USER</a></li> </ul> </li> -<li><a href="#unregister_user_statement">3.53. UNREGISTER USER Statement</a> +<li><a href="#update_statement">3.53. UPDATE Statement</a> <ul class="sectlevel3"> -<li><a href="#unregister_user_syntax">3.53.1. Syntax Description of UNREGISTER USER</a></li> -<li><a href="#unregister_user_considerations">3.53.2. Considerations for UNREGISTER USER</a></li> -<li><a href="#unregister_user_examples">3.53.3. Examples of UNREGISTER USER</a></li> +<li><a href="#update_syntax">3.53.1. Syntax Description of UPDATE</a></li> +<li><a href="#update_considerations">3.53.2. Considerations for UPDATE</a></li> +<li><a href="#update_examples">3.53.3. Examples of UPDATE</a></li> </ul> </li> -<li><a href="#update_statement">3.54. UPDATE Statement</a> +<li><a href="#upsert_statement">3.54. UPSERT Statement</a> <ul class="sectlevel3"> -<li><a href="#update_syntax">3.54.1. Syntax Description of UPDATE</a></li> -<li><a href="#update_considerations">3.54.2. Considerations for UPDATE</a></li> -<li><a href="#update_examples">3.54.3. Examples of UPDATE</a></li> +<li><a href="#upsert_syntax">3.54.1. Syntax Description of UPSERT</a></li> +<li><a href="#upsert_examples">3.54.2. Examples of UPSERT</a></li> </ul> </li> -<li><a href="#upsert_statement">3.55. UPSERT Statement</a> +<li><a href="#values_statement">3.55. VALUES Statement</a> <ul class="sectlevel3"> -<li><a href="#upsert_syntax">3.55.1. Syntax Description of UPSERT</a></li> -<li><a href="#upsert_examples">3.55.2. Examples of UPSERT</a></li> -</ul> -</li> -<li><a href="#values_statement">3.56. VALUES Statement</a> -<ul class="sectlevel3"> -<li><a href="#values_syntax">3.56.1. Syntax Description of VALUES</a></li> -<li><a href="#values_considerations">3.56.2. Considerations for VALUES</a></li> -<li><a href="#values_examples">3.56.3. Examples of VALUES</a></li> +<li><a href="#values_syntax">3.55.1. Syntax Description of VALUES</a></li> +<li><a href="#values_considerations">3.55.2. Considerations for VALUES</a></li> +<li><a href="#values_examples">3.55.3. Examples of VALUES</a></li> </ul> </li> </ul> @@ -3363,10 +3356,6 @@ transaction (BEGIN WORK…COMMIT WORK) or when AUTOCOMMIT is OFF. To run the <td class="tableblock halign-left valign-top"><p class="tableblock">What It Does</p></td> </tr> <tr> -<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="#alter_library_statement">ALTER LIBRARY Statement</a></p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Updates the physical filename for a library object in a Trafodion database.</p></td> -</tr> -<tr> <td class="tableblock halign-left valign-top"><p class="tableblock"><a href="#alter_table_statement">ALTER TABLE Statement</a></p></td> <td class="tableblock halign-left valign-top"><p class="tableblock">Changes attributes for a table.</p></td> </tr> @@ -3628,10 +3617,6 @@ authorization to access libraries or to execute SPJs or UDFs:</p> </thead> <tbody> <tr> -<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="#alter_library_statement">ALTER LIBRARY Statement</a></p></td> -<td class="tableblock halign-left valign-top"><p class="tableblock">Updates the physical filename for a library object in a Trafodion database.</p></td> -</tr> -<tr> <td class="tableblock halign-left valign-top"><p class="tableblock"><a href="#call_statement">CALL Statement</a></p></td> <td class="tableblock halign-left valign-top"><p class="tableblock">Initiates the execution of a stored procedure in Java (SPJ) in a Trafodion database.</p></td> </tr> @@ -3824,127 +3809,7 @@ within a table. These statistics are used to devise optimized access plans.</p>< </div> </div> <div class="sect2"> -<h3 id="alter_library_statement">3.2. ALTER LIBRARY Statement</h3> -<div class="paragraph"> -<p>The ALTER LIBRARY statement updates the physical filename for a library object in a Trafodion database. -A library object can be an SPJ’s JAR file or a UDF’s library file.</p> -</div> -<div class="paragraph"> -<p>ALTER LIBRARY is a Trafodion SQL extension.</p> -</div> -<div class="admonitionblock note"> -<table> -<tr> -<td class="icon"> -<i class="fa icon-note" title="Note"></i> -</td> -<td class="content"> -DDL statements are not currently supported in transactions. That means that you cannot run this statement inside -user-defined transaction (<code>BEGIN WORK…COMMIT WORK</code>) or when AUTOCOMMIT is OFF. To run this statement, AUTOCOMMIT must be -turned ON (the default) for the session. -</td> -</tr> -</table> -</div> -<div class="listingblock"> -<div class="content"> -<pre class="CodeRay highlight"><code data-lang="text">ALTER LIBRARY [[catalog-name.]schema-name.]library-name - file library-filename - [host name host-name] - [local file host-filename]</code></pre> -</div> -</div> -<div class="sect3"> -<h4 id="alter_library_syntax">3.2.1. Syntax Description of ALTER LIBRARY</h4> -<div class="ulist"> -<ul> -<li> -<p><code><em class="[_catalog-name_.">schema-name</em>.]<em>library-name</em></code></p> -<div class="paragraph"> -<p>specifies the ANSI logical name of the library object, where each part of the name is a valid sql identifier with a maximum of 128 characters. -specify the name of a library object that has already been registered in the schema. if you do not fully qualify the library name, trafodion sql -qualifies it according to the schema of the current session. for more information, see <a href="#identifiers">identifiers</a> and -<a href="#_database_object_names">database object names</a>.</p> -</div> -</li> -<li> -<p><code>file <em>library-filename</em></code></p> -<div class="paragraph"> -<p>specifies the full path of the redeployed library file, which either an SPJ’s jar file or a UDF’s library file.</p> -</div> -</li> -<li> -<p><code>host name <em>host-name</em></code></p> -<div class="paragraph"> -<p>specifies the name of the client host machine where the deployed file resides.</p> -</div> -</li> -<li> -<p><code>local file <em>host-filename</em></code></p> -<div class="paragraph"> -<p>specifies the path on the client host machine where the deployed file is stored.</p> -</div> -</li> -</ul> -</div> -<div style="page-break-after: always;"></div> -</div> -<div class="sect3"> -<h4 id="alter_library_considerations">3.2.2. Considerations for ALTER LIBRARY</h4> -<div class="ulist"> -<ul> -<li> -<p>HOST NAME and LOCAL FILE are position dependent.</p> -</li> -</ul> -</div> -<div class="sect4"> -<h5 id="_required_privileges">Required Privileges</h5> -<div class="paragraph"> -<p>To issue an ALTER LIBRARY statement, one of the following must be true:</p> -</div> -<div class="ulist"> -<ul> -<li> -<p>You are DB ROOT.</p> -</li> -<li> -<p>You are the owner of the library.</p> -</li> -<li> -<p>You have the ALTER or ALTER_LIBRARY component privilege for the SQL_OPERATIONS component.</p> -</li> -</ul> -</div> -</div> -</div> -<div class="sect3"> -<h4 id="alter_library_examples">3.2.3. Examples of ALTER LIBRARY</h4> -<div class="ulist"> -<ul> -<li> -<p>This ALTER LIBRARY statement updates the JAR file (SPJs) for a library named SALESLIB in the SALES schema:</p> -<div class="listingblock"> -<div class="content"> -<pre class="CodeRay highlight"><code data-lang="text">ALTER LIBRARY sales.saleslib FILE Sales2.jar;`</code></pre> -</div> -</div> -</li> -<li> -<p>This ALTER LIBRARY statement updates the library file (UDFs) for a library named MYUDFS in the default schema:</p> -<div class="listingblock"> -<div class="content"> -<pre class="CodeRay highlight"><code data-lang="text">ALTER LIBRARY myudfs FILE $TMUDFLIB;</code></pre> -</div> -</div> -</li> -</ul> -</div> -<div style="page-break-after: always;"></div> -</div> -</div> -<div class="sect2"> -<h3 id="alter_table_statement">3.3. ALTER TABLE Statement</h3> +<h3 id="alter_table_statement">3.2. ALTER TABLE Statement</h3> <div class="paragraph"> <p>The ALTER TABLE statement changes a Trafodion SQL table. See <a href="#tables">Tables</a>.</p> </div> @@ -4040,7 +3905,7 @@ column-list is: </div> <div style="page-break-after: always;"></div> <div class="sect3"> -<h4 id="alter_table_syntax">3.3.1. Syntax Description of ALTER TABLE</h4> +<h4 id="alter_table_syntax">3.2.1. Syntax Description of ALTER TABLE</h4> <div class="ulist"> <ul> <li> @@ -4338,7 +4203,7 @@ a.b.c might be assigned a name such as a.b.c_123…_01….</p> <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="alter_table_considerations">3.3.2. Considerations for ALTER TABLE</h4> +<h4 id="alter_table_considerations">3.2.2. Considerations for ALTER TABLE</h4> <div class="sect4"> <h5 id="effect_of_adding_a_column_on_view_definitions">Effect of Adding a Column on View Definitions</h5> <div class="paragraph"> @@ -4352,7 +4217,7 @@ definitions are replaced by explicit column references when the definition claus <p>ALTER TABLE works only on user-created tables.</p> </div> <div class="sect5"> -<h6 id="_required_privileges_2">Required Privileges</h6> +<h6 id="_required_privileges">Required Privileges</h6> <div class="paragraph"> <p>To issue an ALTER TABLE statement, one of the following must be true:</p> </div> @@ -4406,7 +4271,7 @@ following must be true:</p> </div> </div> <div class="sect3"> -<h4 id="alter_table_examples">3.3.3. Example of ALTER TABLE</h4> +<h4 id="alter_table_examples">3.2.3. Example of ALTER TABLE</h4> <div class="paragraph"> <p>This example adds a column:</p> </div> @@ -4421,7 +4286,7 @@ following must be true:</p> </div> </div> <div class="sect2"> -<h3 id="alter_user_statement">3.4. ALTER USER Statement</h3> +<h3 id="alter_user_statement">3.3. ALTER USER Statement</h3> <div class="paragraph"> <p>The ALTER USER statement changes attributes associated with a user who is registered in the database.</p> </div> @@ -4438,7 +4303,7 @@ alter-action is: </div> </div> <div class="sect3"> -<h4 id="alter_user_syntax">3.4.1. Syntax Description of ALTER USER</h4> +<h4 id="alter_user_syntax">3.3.1. Syntax Description of ALTER USER</h4> <div class="ulist"> <ul> <li> @@ -4495,7 +4360,7 @@ identifier. See <a href="#Case_Insensitive_Delimited_Identifiers">Case-Insensiti <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="alter_user_considerations">3.4.2. Considerations for ALTER USER</h4> +<h4 id="alter_user_considerations">3.3.2. Considerations for ALTER USER</h4> <div class="paragraph"> <p>Only a user with user administrative privileges (that is, a user who has been granted the MANAGE_USERS component privilege) can do the following:</p> @@ -4515,7 +4380,7 @@ can do the following:</p> </div> </div> <div class="sect3"> -<h4 id="alter_user_examples">3.4.3. Examples of ALTER USER</h4> +<h4 id="alter_user_examples">3.3.3. Examples of ALTER USER</h4> <div class="ulist"> <ul> <li> @@ -4540,7 +4405,7 @@ can do the following:</p> </div> </div> <div class="sect2"> -<h3 id="begin_work_statement">3.5. BEGIN WORK Statement</h3> +<h3 id="begin_work_statement">3.4. BEGIN WORK Statement</h3> <div class="paragraph"> <p>The BEGIN WORK statement enables you to start a transaction explicitlyâwhere the transaction consists of the set of operations defined by the sequence of SQL statements that begins immediately after BEGIN WORK and ends with the next COMMIT or ROLLBACK @@ -4555,13 +4420,13 @@ statement. See <a href="#Transaction_Management">Transaction Management</a>. BEG </div> </div> <div class="sect3"> -<h4 id="begin_work_considerations">3.5.1. Considerations for BEGIN WORK</h4> +<h4 id="begin_work_considerations">3.4.1. Considerations for BEGIN WORK</h4> <div class="paragraph"> <p>BEGIN WORK starts a transaction. COMMIT WORK or ROLLBACK WORK ends a transaction.</p> </div> </div> <div class="sect3"> -<h4 id="begin_work_examples">3.5.2. Example of BEGIN WORK</h4> +<h4 id="begin_work_examples">3.4.2. Example of BEGIN WORK</h4> <div class="paragraph"> <p>Group three separate statementsâtwo INSERT statements and an UPDATE statementâthat update the database within a single transaction:</p> </div> @@ -4594,7 +4459,7 @@ COMMIT WORK; </div> </div> <div class="sect2"> -<h3 id="call_statement">3.6. CALL Statement</h3> +<h3 id="call_statement">3.5. CALL Statement</h3> <div class="paragraph"> <p>The CALL statement invokes a stored procedure in Java (SPJ) in a Trafodion SQL database.</p> </div> @@ -4610,7 +4475,7 @@ argument-list is: </div> </div> <div class="sect3"> -<h4 id="call_syntax">3.6.1. Syntax Description of CALL</h4> +<h4 id="call_syntax">3.5.1. Syntax Description of CALL</h4> <div class="ulist"> <ul> <li> @@ -4619,7 +4484,7 @@ argument-list is: <p>specifies an ANSI logical name of the form:</p> </div> <div class="paragraph"> -<p><code><em class="[_catalog-name_.">schema-name</em>.]<em>procedure-name</em></code></p> +<p><code>[[_catalog-name_.]<em>schema-name</em>.]<em>procedure-name</em></code></p> </div> <div class="paragraph"> <p>where each part of the name is a valid sql identifier with a maximum of 128 characters. for more information, see @@ -4668,7 +4533,7 @@ separated by commas:</p> </div> </div> <div class="sect3"> -<h4 id="call_considerations">3.6.2. Considerations for CALL</h4> +<h4 id="call_considerations">3.5.2. Considerations for CALL</h4> <div class="sect4"> <h5 id="call_usage_restrictions">Usage Restrictions</h5> <div class="paragraph"> @@ -4769,7 +4634,7 @@ a CALL statement does not always automatically abort the transaction.</p> </div> </div> <div class="sect3"> -<h4 id="call_examples">3.6.3. Examples of CALL</h4> +<h4 id="call_examples">3.5.3. Examples of CALL</h4> <div class="ulist"> <ul> <li> @@ -4835,7 +4700,7 @@ ORDERNUM PARTNUM UNIT_PRICE QTY_ORDERED PARTDESC </div> </div> <div class="sect2"> -<h3 id="commit_work_statement">3.7. COMMIT WORK Statement</h3> +<h3 id="commit_work_statement">3.6. COMMIT WORK Statement</h3> <div class="paragraph"> <p>The COMMIT WORK statement commits any changes to objects made during the current transaction and ends the transaction. See <a href="#Transaction_Management">Transaction Management</a>.</p> @@ -4852,14 +4717,14 @@ the transaction. See <a href="#Transaction_Management">Transaction Management</a </div> </div> <div class="sect3"> -<h4 id="commit_work_considerations">3.7.1. Considerations for COMMIT WORK</h4> +<h4 id="commit_work_considerations">3.6.1. Considerations for COMMIT WORK</h4> <div class="paragraph"> <p>BEGIN WORK starts a transaction. COMMIT WORK or ROLLBACK WORK ends a transaction.</p> </div> <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="commit_work_examples">3.7.2. Example of COMMIT WORK</h4> +<h4 id="commit_work_examples">3.6.2. Example of COMMIT WORK</h4> <div class="paragraph"> <p>Suppose that your application adds information to the inventory. You have received 24 terminals from a new supplier and want to add the supplier and update the quantity on hand. The part number for the @@ -4907,7 +4772,7 @@ COMMIT WORK; </div> </div> <div class="sect2"> -<h3 id="control_query_cancel_statement">3.8. CONTROL QUERY CANCEL Statement</h3> +<h3 id="control_query_cancel_statement">3.7. CONTROL QUERY CANCEL Statement</h3> <div class="paragraph"> <p>The CONTROL QUERY CANCEL statement cancels an executing query that you identify with a query ID. You can execute the CONTROL QUERY CANCEL statement in a client-based tool like TrafCI or through any ODBC or JDBC @@ -4922,7 +4787,7 @@ application.</p> </div> </div> <div class="sect3"> -<h4 id="control_query_cancel_syntax">3.8.1. Syntax Description of CONTROL QUERY CANCEL</h4> +<h4 id="control_query_cancel_syntax">3.7.1. Syntax Description of CONTROL QUERY CANCEL</h4> <div class="ulist"> <ul> <li> @@ -4941,7 +4806,7 @@ application.</p> </div> </div> <div class="sect3"> -<h4 id="control_query_cancel_considerations">3.8.2. Considerations for CONTROL QUERY CANCEL</h4> +<h4 id="control_query_cancel_considerations">3.7.2. Considerations for CONTROL QUERY CANCEL</h4> <div class="sect4"> <h5 id="control_query_cancel_benefitsl">Benefits of CONTROL QUERY CANCEL</h5> <div class="paragraph"> @@ -5028,7 +4893,7 @@ and rarely with other statements.</p> </div> </div> <div class="sect3"> -<h4 id="control_query_cancel_examples">3.8.3. Example of CONTROL QUERY CANCEL</h4> +<h4 id="control_query_cancel_examples">3.7.3. Example of CONTROL QUERY CANCEL</h4> <div class="paragraph"> <p>This CONTROL QUERY CANCEL statement cancels a specified query and provides a comment concerning the cancel operation:</p> @@ -5055,7 +4920,7 @@ error message indicating that the query has been canceled:</p> </div> </div> <div class="sect2"> -<h3 id="control_query_default_statement">3.9. CONTROL QUERY DEFAULT Statement</h3> +<h3 id="control_query_default_statement">3.8. CONTROL QUERY DEFAULT Statement</h3> <div class="paragraph"> <p>The CONTROL QUERY DEFAULT statement changes the default settings for the current process. You can execute the CONTROL QUERY DEFAULT statement in a client-based tool like TrafCI or through any ODBC or JDBC application.</p> @@ -5072,7 +4937,7 @@ control-default-option is: </div> </div> <div class="sect3"> -<h4 id="control_query_default_syntax">3.9.1. Syntax Description of CONTROL QUERY DEFAULT</h4> +<h4 id="control_query_default_syntax">3.8.1. Syntax Description of CONTROL QUERY DEFAULT</h4> <div class="ulist"> <ul> <li> @@ -5101,7 +4966,7 @@ to be reset to the value or values in effect at the start of the current session <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="control_query_default_considerations">3.9.2. Considerations for CONTROL QUERY DEFAULT</h4> +<h4 id="control_query_default_considerations">3.8.2. Considerations for CONTROL QUERY DEFAULT</h4> <div class="sect4"> <h5 id="control_query_default_scope">Scope of CONTROL QUERY DEFAULT</h5> <div class="paragraph"> @@ -5125,7 +4990,7 @@ EXECUTE y; -- uses MYSCHEMA;</code></pre> </div> </div> <div class="sect3"> -<h4 id="control_query_default_examples">3.9.3. Examples of CONTROL QUERY DEFAULT</h4> +<h4 id="control_query_default_examples">3.8.3. Examples of CONTROL QUERY DEFAULT</h4> <div class="ulist"> <ul> <li> @@ -5150,7 +5015,7 @@ EXECUTE y; -- uses MYSCHEMA;</code></pre> </div> </div> <div class="sect2"> -<h3 id="create_function_statement">3.10. CREATE FUNCTION Statement</h3> +<h3 id="create_function_statement">3.9. CREATE FUNCTION Statement</h3> <div class="paragraph"> <p>The CREATE FUNCTION statement registers a user-defined function (UDF) written in C as a function within a Trafodion database. Currently, Trafodion supports the creation of <em>scalar UDFs</em>, which return a single @@ -5198,7 +5063,7 @@ return-parameter-declaration is: </div> <div style="page-break-after: always;"></div> <div class="sect3"> -<h4 id="create_function_syntax">3.10.1. Syntax Description of CREATE FUNCTION</h4> +<h4 id="create_function_syntax">3.9.1. Syntax Description of CREATE FUNCTION</h4> <div class="ulist"> <ul> <li> @@ -5214,7 +5079,7 @@ return-parameter-declaration is: <p>specifies an ANSI logical name of the form:</p> </div> <div class="paragraph"> -<p><code><em class="[_catalog-name_.">schema-name</em>.]<em>function-name</em></code></p> +<p><code>[[_catalog-name_.]<em>schema-name</em>.]<em>function-name</em></code></p> </div> <div class="paragraph"> <p>where each part of the name is a valid sql identifier with a maximum of 128 characters. for more information, see @@ -5318,7 +5183,7 @@ trafodion. see <a href="#data_types">data types</a>.</p> </div> </li> <li> -<p><code>library <em class="[_catalog-name_.">schema-name</em>.]<em>library-name</em></code></p> +<p><code>library [[_catalog-name_.]<em>schema-name</em>.]<em>library-name</em></code></p> <div class="paragraph"> <p>specifies the ANSI logical name of a library containing the external function. if you do not fully qualify the library name, trafodion sql qualifies it according to the schema of the current session.</p> @@ -5380,7 +5245,7 @@ bytes. acceptable values range from 0 to 16000. the default is no state area.</p <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_function_considerations">3.10.2. Considerations for CREATE FUNCTION</h4> +<h4 id="create_function_considerations">3.9.2. Considerations for CREATE FUNCTION</h4> <div class="sect4"> <h5 id="create_function_required_privileges">Required Privileges</h5> <div class="paragraph"> @@ -5423,7 +5288,7 @@ In this case, if you create a function in a private schema, it will be owned by </div> </div> <div class="sect3"> -<h4 id="create_function_examples">3.10.3. Examples of CREATE FUNCTION</h4> +<h4 id="create_function_examples">3.9.3. Examples of CREATE FUNCTION</h4> <div class="ulist"> <ul> <li> @@ -5466,7 +5331,7 @@ five input integers:</p> </div> </div> <div class="sect2"> -<h3 id="create_index_statement">3.11. CREATE INDEX Statement</h3> +<h3 id="create_index_statement">3.10. CREATE INDEX Statement</h3> <div class="paragraph"> <p>The CREATE INDEX statement creates an SQL index based on one or more columns of a table or table-like object. The CREATE VOLATILE INDEX statement creates an SQL index with a lifespan that is limited to the SQL session that @@ -5502,7 +5367,7 @@ hbase-options-list is: </div> </div> <div class="sect3"> -<h4 id="create_index_syntax">3.11.1. Syntax Description of CREATE INDEX</h4> +<h4 id="create_index_syntax">3.10.1. Syntax Description of CREATE INDEX</h4> <div class="ulist"> <ul> <li> @@ -5679,7 +5544,7 @@ KeyPrefixRegionSplitPolicy'</p></td> <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_index_considerations">3.11.2. Considerations for CREATE INDEX</h4> +<h4 id="create_index_considerations">3.10.2. Considerations for CREATE INDEX</h4> <div class="paragraph"> <p>Indexes are created under a single transaction. When an index is created, the following steps occur:</p> </div> @@ -5788,7 +5653,7 @@ the clustering key of the underlying table cannot exceed 2048 bytes.</p> </div> </div> <div class="sect3"> -<h4 id="create_index_examples">3.11.3. Examples of CREATE INDEX</h4> +<h4 id="create_index_examples">3.10.3. Examples of CREATE INDEX</h4> <div class="ulist"> <ul> <li> @@ -5806,7 +5671,7 @@ ON persnl.employee (last_name, first_name);</code></pre> </div> </div> <div class="sect2"> -<h3 id="create_library_statement">3.12. CREATE LIBRARY Statement</h3> +<h3 id="create_library_statement">3.11. CREATE LIBRARY Statement</h3> <div class="paragraph"> <p>The CREATE LIBRARY statement registers a library object in a Trafodion database. A library object can be an SPJ’s JAR file or a UDF’s library file.</p> @@ -5837,11 +5702,11 @@ is OFF. To run this statement, AUTOCOMMIT must be turned ON (the default) for th </div> </div> <div class="sect3"> -<h4 id="create_library_syntax">3.12.1. Syntax Description of CREATE LIBRARY</h4> +<h4 id="create_library_syntax">3.11.1. Syntax Description of CREATE LIBRARY</h4> <div class="ulist"> <ul> <li> -<p><code><em class="[_catalog-name_.">schema-name</em>.]<em>library-name</em></code></p> +<p><code>[[_catalog-name_.]<em>schema-name</em>.]<em>library-name</em></code></p> <div class="paragraph"> <p>specifies the ANSI logical name of the library object, where each part of the name is a valid sql identifier with a maximum of 128 characters. specify a name that is unique and does not exist for @@ -5882,7 +5747,7 @@ will see an error message indicating that the jar or dll file was not found.</p> </div> </div> <div class="sect3"> -<h4 id="create_library_considerations">3.12.2. Considerations for CREATE LIBRARY</h4> +<h4 id="create_library_considerations">3.11.2. Considerations for CREATE LIBRARY</h4> <div class="ulist"> <ul> <li> @@ -5938,7 +5803,7 @@ In this case, if you create a library in a private schema, it will be owned by t </div> </div> <div class="sect3"> -<h4 id="create_library_examples">3.12.3. Examples of CREATE LIBRARY</h4> +<h4 id="create_library_examples">3.11.3. Examples of CREATE LIBRARY</h4> <div class="ulist"> <ul> <li> @@ -5963,7 +5828,7 @@ In this case, if you create a library in a private schema, it will be owned by t </div> </div> <div class="sect2"> -<h3 id="create_procedure_statement">3.13. CREATE PROCEDURE Statement</h3> +<h3 id="create_procedure_statement">3.12. CREATE PROCEDURE Statement</h3> <div class="paragraph"> <p>The CREATE PROCEDURE statement registers a Java method as a stored procedure in Java (SPJ) within a Trafodion database.</p> </div> @@ -6038,7 +5903,7 @@ the remaining syntax is not case-sensitive. </table> </div> <div class="sect3"> -<h4 id="create_procedure_syntax">3.13.1. Syntax Description of CREATE PROCEDURE</h4> +<h4 id="create_procedure_syntax">3.12.1. Syntax Description of CREATE PROCEDURE</h4> <div class="ulist"> <ul> <li> @@ -6055,25 +5920,25 @@ the SPJ method.</p> <p>specifies an ANSI logical name of the form:</p> </div> <div class="paragraph"> -<p><code><em class="[_catalog-name_.">schema-name</em>.]<em>procedure-name</em></code></p> +<p><code>[[_catalog-name_.]<em>schema-name</em>.]<em>procedure-name</em></code></p> </div> <div class="paragraph"> -<p>where each part of the name is a valid sql identifier with a maximum of 128 characters. for more information, +<p>where each part of the name is a valid SQL identifier with a maximum of 128 characters. For more information, see <a href="#identifiers">identifiers</a> and <a href="#database_object_names">database object names</a>.</p> </div> <div class="paragraph"> -<p>specify a name that is unique and does not exist for any procedure or function in the same schema. trafodion sql -does not support the overloading of procedure names. that is, you cannot register the same procedure name more than +<p>specify a name that is unique and does not exist for any procedure or function in the same schema. Trafodion +does not support the overloading of procedure names. That is, you cannot register the same procedure name more than once with different underlying SPJ methods.</p> </div> <div class="paragraph"> -<p>if you do not fully qualify the procedure name, trafodion sql qualifies it according to the schema of the current session.</p> +<p>If you do not fully qualify the procedure name, then Trafodion qualifies it according to the schema of the current session.</p> </div> </li> <li> -<p><em>sql-parameter</em></p> +<p><code><em>sql-parameter</em></code></p> <div class="paragraph"> -<p>specifies an sql parameter that corresponds to the signature of the SPJ method:</p> +<p>specifies an SQL parameter that corresponds to the signature of the SPJ method:</p> </div> <div class="paragraph"> <p><code>[<em>parameter-mode</em>] [<em>sql-identifier</em>] <em>sql-datatype</em></code></p> @@ -6083,7 +5948,7 @@ once with different underlying SPJ methods.</p> <li> <p><code><em>parameter-mode</em></code></p> <div class="paragraph"> -<p>specifies the mode in, out, or inout of a parameter. the default is in.</p> +<p>specifies the mode <code>in</code>, <code>out</code>, or <code>inout</code> of a parameter. The default is <code>in</code>.</p> </div> <div class="ulist"> <ul> @@ -6096,13 +5961,13 @@ once with different underlying SPJ methods.</p> <li> <p><code>out</code></p> <div class="paragraph"> -<p>specifies a parameter that accepts data from an SPJ. the parameter must be an array.</p> +<p>specifies a parameter that accepts data from an SPJ. The parameter must be an array.</p> </div> </li> <li> <p><code>inout</code></p> <div class="paragraph"> -<p>specifies a parameter that passes data to and accepts data from an SPJ. the parameter must be an array.</p> +<p>specifies a parameter that passes data to and accepts data from an SPJ. The parameter must be an array.</p> </div> </li> </ul> @@ -6111,13 +5976,13 @@ once with different underlying SPJ methods.</p> <li> <p><code><em>sql-identifier</em></code></p> <div class="paragraph"> -<p>specifies an sql identifier for the parameter. for more information, see <a href="#identifiers">identifiers</a>.</p> +<p>specifies an SQL identifier for the parameter. For more information, see <a href="#identifiers">identifiers</a>.</p> </div> </li> <li> <p><code><em>sql-datatype</em></code></p> <div class="paragraph"> -<p>specifies an sql data type that corresponds to the java parameter of the SPJ method.</p> +<p>specifies an SQL data type that corresponds to the Java parameter of the SPJ method.</p> </div> <div class="paragraph"> <p><em>sql-datatype</em> can be:</p> @@ -6229,12 +6094,12 @@ only if you specify the wrapper class in the java signature of the external name <p><code><em class="_package-name_.">class-name</em>.<em>method-name</em></code></p> </div> <div class="paragraph"> -<p>the java method must exist in a java class file, <em>class-name</em>.class, within a library registered in the database. -the java method must be defined as public and static and have a return type of void.</p> +<p>The Java method must exist in a Java class file, <em>class-name</em>.class, within a library registered in the database. +The Java method must be defined as <code>public</code> and <code>static</code> and have a return type of <code>void</code>.</p> </div> <div class="paragraph"> -<p>if the class file that contains the SPJ method is part of a package, you must also specify the package name. -if you do not specify the package name, the create procedure statement fails to register the SPJ.</p> +<p>If the class file that contains the SPJ method is part of a package, then you must also specify the package name. +If you do not specify the package name, the create procedure statement fails to register the SPJ.</p> </div> </li> <li> @@ -6246,20 +6111,14 @@ if you do not specify the package name, the create procedure statement fails to <p><code>([<em>java-datatype</em>[, <em>java-datatype</em>]…])</code></p> </div> <div class="paragraph"> -<p>the java signature is necessary only if you want to specify a java wrapper class (for example, java.lang.integer) instead of a java -primitive data type (for example, int). an sql data type maps to a java primitive data type by default.</p> +<p>The Java signature is necessary only if you want to specify a Java wrapper class (for example, <code>java.lang.integer</code>) instead of a java +primitive data type (for example, <code>int</code>). An SQL data type maps to a Java primitive data type by default.</p> </div> <div class="paragraph"> -<p>the java signature is case-sensitive and must be placed within parentheses, such as (java.lang.integer, java.lang.integer). -the signature must specify each of the parameter data types in the order they appear in the java method definition within -the class file. each java data type that corresponds to an out or inout parameter must be followed by empty square -brackets ([ ]), such as java.lang.integer[].</p> -</div> -</li> -</ul> -</div> -</li> -</ul> +<p>The Java signature is case-sensitive and must be placed within parentheses, such as <code>(java.lang.integer, java.lang.integer</code>). +The signature must specify each of the parameter data types in the order they appear in the Java method definition within +the class file. Each Java data type that corresponds to an out or inout parameter must be followed by empty square +brackets (<code>[ ]</code>), such as <code>java.lang.integer[]</code>.</p> </div> <div style="page-break-after: always;"></div> <div class="ulist"> @@ -6267,15 +6126,20 @@ brackets ([ ]), such as java.lang.integer[].</p> <li> <p><code><em>java-datatype</em></code></p> <div class="paragraph"> -<p>specifies a mappable java data type. for the mapping of the java data types to sql data types, see <em>sql-datatype</em>.</p> +<p>Specifies a mappable Java data type. For the mapping of the Java data types to SQL data types, see <em>sql-datatype</em>.</p> </div> -<div class="ulist"> -<ul> +</li> +</ul> +</div> +</li> +</ul> +</div> +</li> <li> -<p><code>library <em class="[_catalog-name_.">schema-name</em>.]<em>library-name</em></code></p> +<p><code>library [[_catalog-name_.]<em>schema-name</em>.]<em>library-name</em></code></p> <div class="paragraph"> -<p>specifies the ANSI logical name of a library containing the SPJ method. if you do not fully qualify the library name, -trafodion sql qualifies it according to the schema of the current session.</p> +<p>specifies the ANSI logical name of a library containing the SPJ method. If you do not fully qualify the library name, +then Trafodion qualifies it according to the schema of the current session.</p> </div> </li> <li> @@ -6287,23 +6151,32 @@ types of external security:</p> <div class="ulist"> <ul> <li> -<p>invoker determines that users can execute, or invoke, the stored procedure using the privileges of the user who invokes -the stored procedure. this behavior is referred to as <em>invoker rights</em> and is the default behavior if external security is -not specified. invoker rights allow a user who has the execute privilege on the SPJ to call the SPJ using his or her existing -privileges. in this case, the user must be granted privileges to access the underlying database objects on which the SPJ operates.</p> -<div class="paragraph"> -<p>note: granting a user privileges to the underlying database objects gives the user direct access to those database objects, -which could pose a risk to more sensitive or critical data to which users should not have access. for example, an SPJ -might operate on a subset of the data in an underlying database object, but that database object might contain other -more sensitive or critical data to which users should not have access.</p> +<p><code>invoker</code> determines that users can execute, or invoke, the stored procedure using the privileges of the user who invokes +the stored procedure. This behavior is referred to as <em>invoker rights</em> and is the default behavior if external security is +not specified. Invoker rights allow a user who has the execute privilege on the SPJ to call the SPJ using his or her existing +privileges. In this case, the user must be granted privileges to access the underlying database objects on which the SPJ operates.</p> +<div class="admonitionblock note"> +<table> +<tr> +<td class="icon"> +<i class="fa icon-note" title="Note"></i> +</td> +<td class="content"> +Granting a user privileges to the underlying database objects gives the user direct access to those database objects, +which could pose a risk to more sensitive or critical data to which users should not have access. For example, an SPJ +might operate on a subset of the data in an underlying database object but that database object might contain other +more sensitive or critical data to which users should not have access. +</td> +</tr> +</table> </div> </li> <li> -<p>definer determines that users can execute, or invoke, the stored procedure using the privileges of the user who created -the stored procedure. this behavior is referred to as <em>definer rights</em>. the advantage of definer rights is that users are +<p><code>definer</code> determines that users can execute, or invoke, the stored procedure using the privileges of the user who created +the stored procedure. This behavior is referred to as <em>definer rights</em>. The advantage of definer rights is that users are allowed to manipulate data by invoking the stored procedure without having to be granted privileges to the underlying -database objects. that way, users are restricted from directly accessing or manipulating more sensitive or critical data in -the database. however, be careful about the users to whom you grant execute privilege on an SPJ with definer external security +database objects. That way, users are restricted from directly accessing or manipulating more sensitive or critical data in +the database. However, be careful about the users to whom you grant execute privilege on an SPJ with definer external security because those users will be able to execute the SPJ without requiring privileges to the underlying database objects.</p> </li> </ul> @@ -6311,9 +6184,6 @@ because those users will be able to execute the SPJ without requiring privileges </li> </ul> </div> -</li> -</ul> -</div> <div style="page-break-after: always;"></div> <div class="ulist"> <ul> @@ -6326,40 +6196,40 @@ because those users will be able to execute the SPJ without requiring privileges <li> <p><code>parameter style java</code></p> <div class="paragraph"> -<p>specifies that the run-time conventions for arguments passed to the external user-defined routine are those of the java language.</p> +<p>specifies that the run-time conventions for arguments passed to the external user-defined routine are those of the Java language.</p> </div> </li> <li> <p><code>no sql</code></p> <div class="paragraph"> -<p>specifies that the SPJ cannot perform sql operations.</p> +<p>specifies that the SPJ cannot perform SQL operations.</p> </div> </li> <li> <p><code>contains sql | modifies sql data | reads sql data</code></p> <div class="paragraph"> -<p>specifies that the SPJ can perform sql operations. all these options behave the same as contains sql, meaning that the SPJ -can read and modify sql data. use one of these options to register a method that contains sql statements. if you do not specify -an sql access mode, the default is contains sql.</p> +<p>specifies that the SPJ can perform SQL operations. All these options behave the same as <code>contains sql</code>, meaning that the SPJ +can read and modify SQL data. Use one of these options to register a method that contains SQL statements. Ff you do not specify +an SQL access mode, then the default is <code>contains sql</code>.</p> </div> </li> <li> <p><code>dynamic result sets <em>integer</em></code></p> <div class="paragraph"> -<p>specifies the maximum number of result sets that the SPJ can return. this option is applicable only if the method signature -contains a java.sql.resultset[] object. if the method contains a result set object, the valid range is 1 to 255 inclusive. -the actual number of result sets returned by the SPJ method can be less than or equal to this number. if you do not specify -this option, the default value is 0 (zero), meaning that the SPJ does not return result sets.</p> +<p>specifies the maximum number of result sets that the SPJ can return. This option is applicable only if the method signature +contains a <code>java.sql.resultset[]</code> object. If the method contains a result set object, then the valid range is 1 to 255 inclusive. +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.</p> </div> </li> <li> <p><code>transaction required | no transaction required</code></p> <div class="paragraph"> -<p>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 will 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, you should set the stored -procedureâs transaction attribute to no transaction required. for more information, see +<p>determines whether the SPJ must run in a transaction inherited from the calling application (<code>transaction required</code>, the default +option) or whether the SPJ runs without inheriting the calling applicationâs transaction (<code>no transaction required</code>). 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 <a href="#effects_of_the_transaction_attribute_on_spjs">effects of the transaction attribute on SPJs</a>.</p> </div> </li> @@ -6372,23 +6242,23 @@ procedureâs transaction attribute to no transaction required. for more informa <p><code>deterministic | not deterministic</code></p> <div class="paragraph"> <p>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, -trafodion sql is not required to call the SPJ each time to produce results; instead, trafodion sql caches the results and -reuses them during subsequent calls, thus optimizing the call statement.</p> +(<code>deterministic</code>) or does not return the same values (<code>not deterministic</code>, the default option). If you specify <code>deterministic</code>, +Trafodion is not required to call the SPJ each time to produce results; instead, Trafodion caches the results and +reuses them during subsequent calls, thus optimizing the CALL statement.</p> </div> </li> <li> <p><code>no isolate | isolate</code></p> <div class="paragraph"> -<p>specifies that the SPJ executes either in the environment of the database server (no isolate) or in an isolated environment -(isolate, the default option). trafodion sql allows both options but always executes the SPJ in the udr server process (isolate).</p> +<p>specifies that the SPJ executes either in the environment of the database server (<code>no isolate</code>) or in an isolated environment +(<code>isolate</code>, the default option). Trafodion allows both options but always executes the SPJ in the UDR server process (<code>isolate</code>).</p> </div> </li> </ul> </div> </div> <div class="sect3"> -<h4 id="create_procedure_considerations">3.13.2. Considerations for CREATE PROCEDURE</h4> +<h4 id="create_procedure_considerations">3.12.2. Considerations for CREATE PROCEDURE</h4> <div class="sect4"> <h5 id="create_procedure_required_privileges">Required Privileges</h5> <div class="paragraph"> @@ -6441,17 +6311,17 @@ In this case, if you create a stored procedure in a private schema, it will be o <p>If you specify TRANSACTION REQUIRED (the default option), a CALL statement automatically initiates a transaction if there is no active transaction. In this case, you should not use transaction control statements (or equivalent JDBC transaction methods) in the SPJ method. Transaction control statements include COMMIT WORK and ROLLBACK WORK, and the equivalent JDBC transaction -methods are Connection.commit() and Connection.rollback(). If you try to use transaction control statements or methods in an -SPJ method when the stored procedureâs transaction attribute is set to TRANSACTION REQUIRED, the transaction control statements +methods are <code>Connection.commit()</code> and <code>Connection.rollback()</code>. If you try to use transaction control statements or methods in an +SPJ method when the stored procedureâs transaction attribute is set to TRANSACTION REQUIRED, then the transaction control statements or methods in the SPJ method are ignored, and the Java virtual machine (JVM) does not report any errors or warnings. When the -stored procedureâs transaction attribute is set to TRANSACTION REQUIRED, you should rely on the transaction control statements +stored procedureâs transaction attribute is set to TRANSACTION REQUIRED, then you should rely on the transaction control statements or methods in the application that calls the stored procedure and allow the calling application to manage the transactions.</p> </div> <div class="paragraph"> <p><em>Committing or Rolling Back a Transaction</em></p> </div> <div class="paragraph"> -<p>If you do not use transaction control statements in the calling application, the transaction initiated by the CALL statement +<p>If you do not use transaction control statements in the calling application, then the transaction initiated by the CALL statement might not automatically commit or roll back changes to the database. When AUTOCOMMIT is ON (the default setting), the database engine automatically commits or rolls back any changes made to the database at the end of the CALL statement execution. However, when AUTOCOMMIT is OFF, the current transaction remains active until the end of the client session or until you explicitly commit @@ -6495,14 +6365,14 @@ procedure.</p> <div class="paragraph"> <p>If you specify NO TRANSACTION REQUIRED and if the SPJ method creates a JDBC default connection, that connection will have autocommit enabled by default. You can either use the autocommit transactions or disable autocommit (conn.setAutoCommit(false);) and use the -JDBC transaction methods, Connection.commit() and Connection.rollback(), to commit or roll back work where needed.</p> +JDBC transaction methods, <code>Connection.commit()</code> and <code>Connection.rollback()</code>, to commit or roll back work where needed.</p> </div> <div style="page-break-after: always;"></div> </div> </div> </div> <div class="sect3"> -<h4 id="create_procedure_examples">3.13.3. Examples of CREATE PROCEDURE</h4> +<h4 id="create_procedure_examples">3.12.3. Examples of CREATE PROCEDURE</h4> <div class="ulist"> <ul> <li> @@ -6520,7 +6390,7 @@ CREATE PROCEDURE lowerprice() </div> </div> <div class="paragraph"> -<p>Because the procedure name is not qualified by a catalog and schema, Trafodion SQL qualifies it according to the current +<p>Because the procedure name is not qualified by a catalog and schema, Trafodion qualifies it according to the current session settings, where the catalog is TRAFODION (by default) and the schema is set to SALES. Since the procedure needs to be able to read and modify SQL data, MODIFIES SQL DATA is specified in the CREATE PROCEDURE statement.</p> </div> @@ -6626,7 +6496,7 @@ returns information about the orders on or after that date.</p> </div> <div class="listingblock"> <div class="content"> -<pre class="CodeRay highlight"><code data-lang="text">CALL neo.sales.ordersummary('01-01-2014', ?);</code></pre> +<pre class="CodeRay highlight"><code data-lang="text">CALL trafodion.sales.ordersummary('01-01-2014', ?);</code></pre> </div> </div> <div class="paragraph"> @@ -6666,7 +6536,7 @@ ORDERNUM PARTNUM UNIT_PRICE QTY_ORDERED PARTDESC </div> </div> <div class="sect2"> -<h3 id="create_role_statement">3.14. CREATE ROLE Statement</h3> +<h3 id="create_role_statement">3.13. CREATE ROLE Statement</h3> <div class="paragraph"> <p>The CREATE ROLE statement creates an SQL role. See <a href="#roles">Roles</a>.</p> </div> @@ -6679,7 +6549,7 @@ grantor is: </div> </div> <div class="sect3"> -<h4 id="create_role_syntax">3.14.1. Syntax Description of CREATE ROLE</h4> +<h4 id="create_role_syntax">3.13.1. Syntax Description of CREATE ROLE</h4> <div class="ulist"> <ul> <li> @@ -6709,7 +6579,7 @@ See <a href="#Case_Insensitive_Delimited_Identifiers">Case-Insensitive Delimited <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_role_considerations">3.14.2. Considerations for CREATE ROLE</h4> +<h4 id="create_role_considerations">3.13.2. Considerations for CREATE ROLE</h4> <div class="ulist"> <ul> <li> @@ -6744,7 +6614,7 @@ See <a href="#Case_Insensitive_Delimited_Identifiers">Case-Insensitive Delimited </div> </div> <div class="sect3"> -<h4 id="create_role_examples">3.14.3. Examples of CREATE ROLE</h4> +<h4 id="create_role_examples">3.13.3. Examples of CREATE ROLE</h4> <div class="ulist"> <ul> <li> @@ -6769,7 +6639,7 @@ See <a href="#Case_Insensitive_Delimited_Identifiers">Case-Insensitive Delimited </div> </div> <div class="sect2"> -<h3 id="create_schema_statement">3.15. CREATE SCHEMA Statement</h3> +<h3 id="create_schema_statement">3.14. CREATE SCHEMA Statement</h3> <div class="paragraph"> <p>The CREATE SCHEMA statement creates a schema in the database. See <a href="#schemas">Schemas</a>.</p> </div> @@ -6799,7 +6669,7 @@ schema-clause is: </div> </div> <div class="sect3"> -<h4 id="create_schema_syntax">3.15.1. Syntax Description of CREATE SCHEMA</h4> +<h4 id="create_schema_syntax">3.14.1. Syntax Description of CREATE SCHEMA</h4> <div class="ulist"> <ul> <li> @@ -6841,7 +6711,7 @@ user becomes the schema owner.</p> </div> </div> <div class="sect3"> -<h4 id="create_schema_considerations">3.15.2. Considerations for CREATE SCHEMA</h4> +<h4 id="create_schema_considerations">3.14.2. Considerations for CREATE SCHEMA</h4> <div class="sect4"> <h5 id="create_schema_reserved_schema_names">Reserved Schema Names</h5> <div class="paragraph"> @@ -6915,7 +6785,7 @@ By default, this privilege is granted to PUBLIC, but it can be revoked by DB ROO </div> </div> <div class="sect3"> -<h4 id="create_schema_examples">3.15.3. Examples of CREATE SCHEMA</h4> +<h4 id="create_schema_examples">3.14.3. Examples of CREATE SCHEMA</h4> <div class="ulist"> <ul> <li> @@ -6959,7 +6829,7 @@ By default, this privilege is granted to PUBLIC, but it can be revoked by DB ROO </div> </div> <div class="sect2"> -<h3 id="create_table_statement">3.16. CREATE TABLE Statement</h3> +<h3 id="create_table_statement">3.15. CREATE TABLE Statement</h3> <div class="paragraph"> <p>The CREATE TABLE statement creates a Trafodion SQL table, which is a mapping of a relational SQL table to an HBase table. The CREATE VOLATILE TABLE statement creates a temporary Trafodion SQL table that exists only during an SQL session. The @@ -7074,7 +6944,7 @@ hbase-options-list is: </div> </div> <div class="sect3"> -<h4 id="create_table_syntax">3.16.1. Syntax Description of CREATE TABLE</h4> +<h4 id="create_table_syntax">3.15.1. Syntax Description of CREATE TABLE</h4> <div class="ulist"> <ul> <li> @@ -7502,7 +7372,7 @@ Instead, Trafodion SQL generates new names based on the physical file location.< <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_table_considerations">3.16.2. Considerations for CREATE TABLE</h4> +<h4 id="create_table_considerations">3.15.2. Considerations for CREATE TABLE</h4> <div class="paragraph"> <p>The following subsections provide considerations for various CREATE TABLE options:</p> </div> @@ -7990,7 +7860,7 @@ the CREATE TABLE AS … NO LOAD statement. For example:</p> </div> </div> <div class="sect3"> -<h4 id="create_table_trafodion_sql_extensions_to_create_table">3.16.3. Trafodion SQL Extensions to CREATE TABLE</h4> +<h4 id="create_table_trafodion_sql_extensions_to_create_table">3.15.3. Trafodion SQL Extensions to CREATE TABLE</h4> <div class="paragraph"> <p>This statement is supported for compliance with ANSI SQL:1999 Entry Level. Trafodion SQL extensions to the CREATE TABLE statement are ASCENDING, DESCENDING, and PARTITION clauses. CREATE TABLE LIKE is also an extension.</p> @@ -7998,7 +7868,7 @@ statement are ASCENDING, DESCENDING, and PARTITION clauses. CREATE TABLE LIKE is <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_table_examples">3.16.4. Examples of CREATE TABLE</h4> +<h4 id="create_table_examples">3.15.4. Examples of CREATE TABLE</h4> <div class="ulist"> <ul> <li> @@ -8181,7 +8051,7 @@ CREATE TABLE t2 (c1 int, c2 char (50) UPSHIFT NOT NULL) AS SELECT * FROM t1;</co </div> </div> <div class="sect2"> -<h3 id="create_view_statement">3.17. CREATE VIEW Statement</h3> +<h3 id="create_view_statement">3.16. CREATE VIEW Statement</h3> <div class="paragraph"> <p>The CREATE VIEW statement creates a Trafodion SQL view. See <a href="#views">Views</a>.</p> </div> @@ -8208,7 +8078,7 @@ must be turned ON (the default) for the session. </div> </div> <div class="sect3"> -<h4 id="create_view_syntax">3.17.1. Syntax Description of CREATE VIEW</h4> +<h4 id="create_view_syntax">3.16.1. Syntax Description of CREATE VIEW</h4> <div class="ulist"> <ul> <li> @@ -8284,7 +8154,7 @@ row is inserted or updated.</p> <div style="page-break-after: always;"></div> </div> <div class="sect3"> -<h4 id="create_view_considerations">3.17.2. Considerations for CREATE VIEW</h4> +<h4 id="create_view_considerations">3.16.2. Considerations for CREATE VIEW</h4> <div class="ulist"> <ul> <li> @@ -8530,7 +8400,7 @@ select * from v2;</code></pre> </div> </div> <div class="sect3"> -<h4 id="create_view_examples">3.17.3. Examples of CREATE VIEW</h4> +<h4 id="create_view_examples">3.16.3. Examples of CREATE VIEW</h4> <div class="ulist"> <ul> <li> @@ -8634,7 +8504,7 @@ select d from vp; -- reads vp0 and vp2</code></pre> </div> </div> <div class="sect2"> -<h3 id="delete_statement">3.18. DELETE Statement</h3> +<h3 id="delete_statement">3.17. DELETE Statement</h3> <div class="paragraph"> <p>The DELETE statement is a DML statement that deletes a row or rows from a table or an updatable view. Deleting rows from a view deletes the rows from the table on which the view is based. DELETE does not remove a table or view, even if you @@ -8660,7 +8530,7 @@ access-option is: </div> </div> <div class="sect3"> -<h4 id="delete_syntax">3.18.1. Syntax Description of DELETE</h4> +<h4 id="delete_syntax">3.17.1. Syntax Description of DELETE</h4> <div class="ulist"> <ul> <li> @@ -8704,7 +8574,7 @@ See <a href="#data_consistency_and_access_options">Data Consistency and Access O </div> </div> <div class="sect3"> -<h4 id="delete_considerations">3.18.2. Considerations for DELETE</h4> +<h4 id="delete_considerations">3.17.2. Considerations for DELETE</h4> <div class="sect4"> <h
<TRUNCATED>
