Merge pull request #4385 from EnterpriseDB/content/docs/epas/15/sql_r…

…eference EPAS - 15 SQL reference re-org
EnterpriseDB · Jul 12, 2023 · 8d7e2b6 · 8d7e2b6
2 parents 56d9410 + 592dcf7
commit 8d7e2b6
Show file tree

Hide file tree

Showing 37 changed files with 24 additions and 45 deletions.
diff --git a/...ms/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/...ms/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx
@@ -33,7 +33,7 @@ However, certain data types have alternative names referred to as *aliases*, whi
 
 For example, you can specify fixed-length character data types as `CHAR` or `CHARACTER`. You can specify variable-length character data types as `CHAR VARYING`, `CHARACTER VARYING`, `VARCHAR`, or `VARCHAR2`. For integers, there are `BINARY_INTEGER`, `PLS_INTEGER`, and `INTEGER` data types. For numbers, there are `NUMBER`, `NUMERIC`, `DEC`, and `DECIMAL` data types.
 
-For detailed information about the data types supported by EDB Postgres Advanced Server, see [Data types](../../../../reference/sql_reference/02_the_sql_language/02_data_types/).
+For detailed information about the data types supported by EDB Postgres Advanced Server, see [Data types](../../../../reference/sql_reference/02_data_types/).
 
 Thus, when attempting to create overloaded subprograms, the formal parameter data types aren't considered different if the specified data types are aliases of each other.
 

diff --git a/...docs/epas/15/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx b/...docs/epas/15/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx
@@ -17,9 +17,9 @@ EDB Postgres Advanced Server makes Postgres look, feel, and operate more like Or
 
 EDB Postgres Advanced Server provides Oracle compatible:
 - [Stored procedure language (SPL)](/epas/latest/application_programming/epas_compat_spl/) when creating database server-side application logic for stored procedures, functions, triggers, and packages   
-- [Data types that are compatible with Oracle databases](/epas/latest/reference/sql_reference/02_the_sql_language/02_data_types/)
-- [SQL statements](/epas/latest/reference/sql_reference/02_the_sql_language/01_sql_syntax/) that are compatible with Oracle SQL
-- [System and built-in functions](/epas/latest/reference/sql_reference/02_the_sql_language/03_functions_and_operators/) for use in SQL statements and procedural logic
+- [Data types that are compatible with Oracle databases](/epas/latest/reference/sql_reference/02_data_types/)
+- [SQL statements](/epas/latest/reference/sql_reference/01_sql_syntax/) that are compatible with Oracle SQL
+- [System and built-in functions](/epas/latest/reference/sql_reference/03_functions_and_operators/) for use in SQL statements and procedural logic
 - [System catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/)  that are compatible with Oracle’s data dictionary
 - [Additional compatibility with Oracle MERGE](/epas/latest/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx). 
 

diff --git a/...s/epas/15/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx b/...s/epas/15/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx
@@ -12,9 +12,9 @@ redirects:
 
 EDB Postgres Advanced Server supports SQL language that's compatible with Oracle syntax as well as syntax and commands for extended functionality. Extended functionality doesn't provide database compatibility for Oracle or support Oracle-styled applications.
 
-[SQL reference](/epas/latest/reference/sql_reference/02_the_sql_language/) provides detailed information about:
+[SQL reference](/epas/latest/reference/sql_reference/) provides detailed information about:
 
--   [Compatible SQL syntax and language elements](/epas/latest/reference/sql_reference/02_the_sql_language/01_sql_syntax/)
--   [Data types](/epas/latest/reference/sql_reference/02_the_sql_language/02_data_types/)
--   [Functions and operators for the built-in data types](/epas/latest/reference/sql_reference/02_the_sql_language/03_functions_and_operators/)
+-   [Compatible SQL syntax and language elements](/epas/latest/reference/sql_reference/01_sql_syntax/)
+-   [Data types](/epas/latest/reference/sql_reference/02_data_types/)
+-   [Functions and operators for the built-in data types](/epas/latest/reference/sql_reference/03_functions_and_operators/)
 
diff --git a/product_docs/docs/epas/15/index.mdx b/product_docs/docs/epas/15/index.mdx
@@ -35,9 +35,9 @@ EDB is the only worldwide company to deliver innovative and low-cost, open-sourc
 - [Advanced replication (version 14 and higher)](https://www.enterprisedb.com/docs/pgd/latest/). 
 
 All of these features are available in Postgres mode and [Oracle compatibility mode](/epas/latest/working_with_oracle_data). When you launch EDB Postgres Advanced Server in Oracle compatibility mode, you get additional features that help with Oracle-to-Postgres migrations.
-- [Oracle-compatible custom data types](/epas/latest/reference/sql_reference/02_the_sql_language/02_data_types/)
-- [Oracle keywords](/epas/latest/reference/sql_reference/02_the_sql_language/01_sql_syntax/)
-- [Oracle functions](/epas/latest/reference/sql_reference/02_the_sql_language/03_functions_and_operators/)
+- [Oracle-compatible custom data types](/epas/latest/reference/sql_reference/02_data_types/)
+- [Oracle keywords](/epas/latest/reference/sql_reference/01_sql_syntax/)
+- [Oracle functions](/epas/latest/reference/sql_reference/03_functions_and_operators/)
 - [Orace-style catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/)
 - [Additional compatibility with Oracle MERGE](/epas/latest/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx). 
 

diff --git a/...reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx b/...reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx
@@ -29,7 +29,7 @@ CREATE SEQUENCE <name> [ INCREMENT BY <increment> ]
 
 If you include a schema name, then the sequence is created in the specified schema. Otherwise it's created in the current schema. The sequence name differ from the name of any other sequence, table, index, or view in the same schema.
 
-After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](../../sql_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/).
+After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](../../sql_reference/03_functions_and_operators/09_sequence_manipulation_functions/).
 
 ## Parameters
 

diff --git a/...15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx b/...15/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx
@@ -99,7 +99,7 @@ You can define table constraints and column constraints. A column constraint is
 
 `data_type`
 
- The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](../../sql_reference/02_the_sql_language/02_data_types/).
+ The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](../../sql_reference/02_data_types/).
 
 `DEFAULT default_expr`
 

diff --git a/...ge/01_sql_syntax/01_lexical_structure.mdx → ...ce/01_sql_syntax/01_lexical_structure.mdx b/...ge/01_sql_syntax/01_lexical_structure.mdx → ...ce/01_sql_syntax/01_lexical_structure.mdx
@@ -26,4 +26,4 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
 
 This is a sequence of three commands, one per line, although that format isn't required. You can enter more than one command on a line, and commands can usually split across lines.
 
-The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../../oracle_compatibility_reference/epas_compat_sql/).
+The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../oracle_compatibility_reference/epas_compat_sql/).
diff --git a/...l_syntax/02_identifiers_and_key_words.mdx → ...l_syntax/02_identifiers_and_key_words.mdx b/...l_syntax/02_identifiers_and_key_words.mdx → ...l_syntax/02_identifiers_and_key_words.mdx
diff --git a/...l_language/01_sql_syntax/03_constants.mdx → ..._reference/01_sql_syntax/03_constants.mdx b/...l_language/01_sql_syntax/03_constants.mdx → ..._reference/01_sql_syntax/03_constants.mdx
diff --git a/...ql_language/01_sql_syntax/04_comments.mdx → ...l_reference/01_sql_syntax/04_comments.mdx b/...ql_language/01_sql_syntax/04_comments.mdx → ...l_reference/01_sql_syntax/04_comments.mdx
diff --git a/..._the_sql_language/01_sql_syntax/index.mdx → ...nce/sql_reference/01_sql_syntax/index.mdx b/..._the_sql_language/01_sql_syntax/index.mdx → ...nce/sql_reference/01_sql_syntax/index.mdx
@@ -8,6 +8,7 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.038.html"
 redirects:
   - ../../../../epas_compat_reference/02_the_sql_language/01_sql_syntax #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/01_sql_syntax
 ---
 
 <div id="sql_syntax" class="registered_link"></div>

diff --git a/...nguage/02_data_types/01_numeric_types.mdx → ...erence/02_data_types/01_numeric_types.mdx b/...nguage/02_data_types/01_numeric_types.mdx → ...erence/02_data_types/01_numeric_types.mdx
diff --git a/...uage/02_data_types/02_character_types.mdx → ...ence/02_data_types/02_character_types.mdx b/...uage/02_data_types/02_character_types.mdx → ...ence/02_data_types/02_character_types.mdx
diff --git a/...language/02_data_types/03_binary_data.mdx → ...eference/02_data_types/03_binary_data.mdx b/...language/02_data_types/03_binary_data.mdx → ...eference/02_data_types/03_binary_data.mdx
diff --git a/...uage/02_data_types/04_date_time_types.mdx → ...ence/02_data_types/04_date_time_types.mdx b/...uage/02_data_types/04_date_time_types.mdx → ...ence/02_data_types/04_date_time_types.mdx
diff --git a/...anguage/02_data_types/05_boolean_type.mdx → ...ference/02_data_types/05_boolean_type.mdx b/...anguage/02_data_types/05_boolean_type.mdx → ...ference/02_data_types/05_boolean_type.mdx
diff --git a/...ql_language/02_data_types/06_xml_type.mdx → ...l_reference/02_data_types/06_xml_type.mdx b/...ql_language/02_data_types/06_xml_type.mdx → ...l_reference/02_data_types/06_xml_type.mdx
diff --git a/..._the_sql_language/02_data_types/index.mdx → ...nce/sql_reference/02_data_types/index.mdx b/..._the_sql_language/02_data_types/index.mdx → ...nce/sql_reference/02_data_types/index.mdx
@@ -8,6 +8,7 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.043.html"
 redirects:
   - ../../../../epas_compat_reference/02_the_sql_language/02_data_types #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/02_data_types
 ---
 
 <div id="data_types" class="registered_link"></div>

diff --git a/product_docs/docs/epas/15/reference/sql_reference/02_the_sql_language/index.mdx b/product_docs/docs/epas/15/reference/sql_reference/02_the_sql_language/index.mdx
diff --git a/...ns_and_operators/01_logical_operators.mdx → ...ns_and_operators/01_logical_operators.mdx b/...ns_and_operators/01_logical_operators.mdx → ...ns_and_operators/01_logical_operators.mdx
diff --git a/...and_operators/02_comparison_operators.mdx → ...and_operators/02_comparison_operators.mdx b/...and_operators/02_comparison_operators.mdx → ...and_operators/02_comparison_operators.mdx
diff --git a/..._mathematical_functions_and_operators.mdx → ..._mathematical_functions_and_operators.mdx b/..._mathematical_functions_and_operators.mdx → ..._mathematical_functions_and_operators.mdx
diff --git a/...ors/04_string_functions_and_operators.mdx → ...ors/04_string_functions_and_operators.mdx b/...ors/04_string_functions_and_operators.mdx → ...ors/04_string_functions_and_operators.mdx
diff --git a/.../05_pattern_matching_string_functions.mdx → .../05_pattern_matching_string_functions.mdx b/.../05_pattern_matching_string_functions.mdx → .../05_pattern_matching_string_functions.mdx
diff --git a/...tern_matching_using_the_like_operator.mdx → ...tern_matching_using_the_like_operator.mdx b/...tern_matching_using_the_like_operator.mdx → ...tern_matching_using_the_like_operator.mdx
diff --git a/...ors/07_data_type_formatting_functions.mdx → ...ors/07_data_type_formatting_functions.mdx b/...ors/07_data_type_formatting_functions.mdx → ...ors/07_data_type_formatting_functions.mdx
diff --git a/.../08_date_time_functions_and_operators.mdx → .../08_date_time_functions_and_operators.mdx b/.../08_date_time_functions_and_operators.mdx → .../08_date_time_functions_and_operators.mdx
diff --git a/...rs/09_sequence_manipulation_functions.mdx → ...rs/09_sequence_manipulation_functions.mdx b/...rs/09_sequence_manipulation_functions.mdx → ...rs/09_sequence_manipulation_functions.mdx
diff --git a/..._operators/10_conditional_expressions.mdx → ..._operators/10_conditional_expressions.mdx b/..._operators/10_conditional_expressions.mdx → ..._operators/10_conditional_expressions.mdx
diff --git a/..._and_operators/11_aggregate_functions.mdx → ..._and_operators/11_aggregate_functions.mdx b/..._and_operators/11_aggregate_functions.mdx → ..._and_operators/11_aggregate_functions.mdx
diff --git a/...and_operators/12_subquery_expressions.mdx → ...and_operators/12_subquery_expressions.mdx b/...and_operators/12_subquery_expressions.mdx → ...and_operators/12_subquery_expressions.mdx
diff --git a/...and_operators/13_identifier_functions.mdx → ...and_operators/13_identifier_functions.mdx b/...and_operators/13_identifier_functions.mdx → ...and_operators/13_identifier_functions.mdx
diff --git a/...ns_and_operators/14_bitwise_functions.mdx → ...ns_and_operators/14_bitwise_functions.mdx b/...ns_and_operators/14_bitwise_functions.mdx → ...ns_and_operators/14_bitwise_functions.mdx
diff --git a/...uage/03_functions_and_operators/index.mdx → ...ence/03_functions_and_operators/index.mdx b/...uage/03_functions_and_operators/index.mdx → ...ence/03_functions_and_operators/index.mdx
@@ -8,6 +8,7 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.128.html"
 redirects:
   - ../../../../epas_compat_reference/02_the_sql_language/03_functions_and_operators #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/03_functions_and_operators
 ---
 
 <div id="functions_and_operators" class="registered_link"></div>

diff --git a/...functions_and_operators/to_multi_byte.mdx → ...functions_and_operators/to_multi_byte.mdx b/...functions_and_operators/to_multi_byte.mdx → ...functions_and_operators/to_multi_byte.mdx
diff --git a/...unctions_and_operators/to_single_byte.mdx → ...unctions_and_operators/to_single_byte.mdx b/...unctions_and_operators/to_single_byte.mdx → ...unctions_and_operators/to_single_byte.mdx
diff --git a/product_docs/docs/epas/15/reference/sql_reference/index.mdx b/product_docs/docs/epas/15/reference/sql_reference/index.mdx
@@ -7,20 +7,18 @@ legacyRedirectsGenerated:
   # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
   - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.001.html"
   - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/toc.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.005.html"
 redirects:
   - ../../epas_compat_reference #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode
+  - ../../reference/sql_reference/02_the_sql_language/
 ---
 
 <div id="introduction" class="registered_link"></div>
 
-Database compatibility for Oracle means that an application runs in an Oracle environment as well as in the EDB Postgres Advanced Server environment with minimal or no changes to the application code.
+This SQL reference information applies to organizations migrating their Oracle applications to use EDB Postgres Advanced Server.
 
-Developing an application that's compatible with Oracle databases in EDB Postgres Advanced Server requires special attention to the features you're using. For example, developing a compatible application means selecting:
+A subset of the EDB Postgres Advanced Server SQL language is compatible with Oracle databases. These SQL syntaxes, data types, and functions work in both EDB Postgres Advanced Server and Oracle.
 
--   Data types to define the application’s database tables that are compatible with Oracle databases
--   SQL statements that are compatible with Oracle SQL
--   System and built-in functions for use in SQL statements and procedural logic that are compatible with Oracle databases
--   Stored procedure language (SPL) to create database server-side application logic for stored procedures, functions, triggers, and packages
--   System catalog views that are compatible with Oracle’s data dictionary
-
-This SQL reference information applies to organizations migrating their Oracle applications to use EDB Postgres Advanced Server.
+!!! Note
+    The EDB Postgres Advanced Server also includes syntax and commands for extended functionality (functionality that doesn't provide database compatibility for Oracle or support Oracle-styled applications) that aren't included here.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,4 +26,4 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');

		This is a sequence of three commands, one per line, although that format isn't required. You can enter more than one command on a line, and commands can usually split across lines.

		The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../../oracle_compatibility_reference/epas_compat_sql/).
		The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../oracle_compatibility_reference/epas_compat_sql/).