Merge pull request #4387 from EnterpriseDB/release/2023-07-11

Release: 2023-07-11
EnterpriseDB · Jul 11, 2023 · 7c8f3b0 · 7c8f3b0 · github-actions · Jul 11, 2023
2 parents 7b4f07d + e41aa75
commit 7c8f3b0
Show file tree

Hide file tree

Showing 112 changed files with 489 additions and 697 deletions.
diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx
@@ -15,5 +15,4 @@ Compatible tools and utility programs can allow a developer to work with Advance
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Database Compatibility for Oracle
-Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/).
+For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/).
diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx
@@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 -   SQL statements that are compatible with Oracle SQL
 -   System catalog views that are compatible with Oracle’s data dictionary
 
-For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/).
+For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/).
 
-The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/).
+The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/).
 
-For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
+For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
 
 For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. For detailed information about using the Open Client Library, see [EDB OCL Connector](/ocl_connector/latest/).
diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx
@@ -15,5 +15,4 @@ Compatible tools and utility programs can allow a developer to work with Advance
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Database Compatibility for Oracle
-Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/).
+For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/).
diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx
@@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 -   SQL statements that are compatible with Oracle SQL
 -   System catalog views that are compatible with Oracle’s data dictionary
 
-For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/).
+For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/).
 
-The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/).
+The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/).
 
-For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
+For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
 
 For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. For detailed information about using the Open Client Library, see the *EDB Postgres Advanced Server OCL Connector Guide*.
diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx
@@ -15,5 +15,4 @@ Compatible tools and utility programs can allow a developer to work with Advance
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Database Compatibility for Oracle
-Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/).
+For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/).
diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx
@@ -19,9 +19,9 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 -   SQL statements that are compatible with Oracle SQL
 -   System catalog views that are compatible with Oracle’s data dictionary
 
-For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/).
+For detailed information about the compatible SQL syntax, data types, and views, see the [SQL reference](/epas/latest/epas_compat_sql/).
 
-The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/).
+The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/).
 
 For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
 

diff --git a/...ct_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/...ct_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx
@@ -51,7 +51,7 @@ The process for implementing Virtual Private Database is as follows:
 1.  Use the `ENABLE_POLICY` procedure to disable or enable an existing policy.
 1.  Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure doesn't drop the policy function or the associated database object.
 
-Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/epas_compat_cat_views/).
+Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Catalog views](/epas/latest/epas_compat_cat_views/).
 
 The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is:
 

diff --git a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx
@@ -7,7 +7,7 @@ legacyRedirectsGenerated:
 
 Built-in packages are provided with EDB Postgres Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege is granted to `PUBLIC` by default.
 
-For information about using the `GRANT` command to provide access to a package, see [Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_sql/).
+For information about using the `GRANT` command to provide access to a package, see [SQL reference](/epas/latest/epas_compat_sql/).
 
 All built-in packages are owned by the special `sys` user that must be specified when granting or revoking privileges on built-in packages:
 

diff --git a/.../epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/.../epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx
@@ -4,7 +4,7 @@ title: "edb_redwood_raw_names"
 
 <div id="edb_redwood_raw_names" class="registered_link"></div>
 
-When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/epas_compat_cat_views/). In addition, quotation marks enclose names that were created with enclosing quotation marks.
+When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Catalog views](/epas/latest/epas_compat_cat_views/). In addition, quotation marks enclose names that were created with enclosing quotation marks.
 
 When `edb_redwood_raw_names` is set to `TRUE`, the database object names are displayed exactly as stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without quotation marks appear in lowercase as expected in PostgreSQL. Names created in quotation marks appear exactly as they were created but without the quotation marks.
 

diff --git a/.../docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx b/.../docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx
@@ -9,7 +9,7 @@ legacyRedirectsGenerated:
 
 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.
 
-[Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_ora_dev_guide) provides detailed information about:
+[SQL reference](/epas/latest/reference/sql_reference/) provides detailed information about:
 
 -   Compatible SQL syntax and language elements
 -   Data types

diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx
@@ -9,6 +9,6 @@ legacyRedirectsGenerated:
 
 <div id="oracle_catalog_views" class="registered_link"></div>
 
-The Oracle catalog views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is available in [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/).
+The Oracle catalog views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is available in [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/).
 
 
diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx
@@ -14,5 +14,5 @@ Compatible tools and utility programs allow you to work with EDB Postgres Advanc
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Database Compatibility for Oracle Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/).
+For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/).
 
diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx
@@ -10,6 +10,6 @@ legacyRedirectsGenerated:
 
 The system catalog tables contain definitions of database objects that are available to EDB Postgres Advanced Server. The layout of the system tables is subject to change. If you're writing an application that depends on information stored in the system tables, it's prudent to use an existing catalog view or create a catalog view to isolate the application from changes to the system table.
 
-For detailed information about the system catalog tables, see the [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/).
+For detailed information about the system catalog tables, see the [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/).
 
 
diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx
@@ -18,9 +18,9 @@ Database compatibility for Oracle means that an application runs in an Oracle en
 -   SQL statements that are compatible with Oracle SQL
 -   System catalog views that are compatible with Oracle’s data dictionary
 
-For detailed information about the compatible SQL syntax, data types, and views, see [Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_sql/).
+For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/).
 
-For the compatibility offered by the procedures and functions that are part of the built-in packages, see [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/).
+For the compatibility offered by the procedures and functions that are part of the built-in packages, see [Built-in packages](/epas/latest/epas_compat_bip_guide/).
 
 For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/).
 

diff --git a/...pas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx b/...pas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx
@@ -24,4 +24,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 [Database Compatibility for Oracle Developers SQL](/epas/latest/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](/epas/latest/epas_compat_sql/).
diff --git a/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx
@@ -17,4 +17,4 @@ A *package* is a named collection of functions, procedures, variables, cursors,
 -   You can declare Other functions, procedures, variables, types, and so on in the package as *private*. Private entities can be referenced and used by function and procedures in the package but not by other external applications. Private entities are for use only by programs in the package.
 -   You can overload function and procedure names in a package. One or more functions or procedures can be defined with the same name but with different signatures. This ability lets you create identically named programs that perform the same job but on different types of input.
 
-For more information about the package support provided by EDB Postgres Advanced Server, see [Database Compatibility for Oracle Developers: Built-in Package](/epas/latest/epas_compat_bip_guide/).
+For more information about the package support provided by EDB Postgres Advanced Server, see [Built-in packages](/epas/latest/epas_compat_bip_guide/).
diff --git a/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx b/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx
@@ -27,7 +27,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 [Database Compatibility for Oracle Developers: Reference](/epas/latest/epas_compat_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](/epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/).
 
 ## Parameters
 

diff --git a/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx
@@ -97,7 +97,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 [Database Compatibility for Oracle Developers: Reference](/epas/latest/epas_compat_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](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/).
 
 `DEFAULT default_expr`
 

diff --git a/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx b/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx
@@ -57,7 +57,7 @@ You must have `SELECT` privilege on a table to read its values. The use of `FOR
 
 `optimizer_hint`
 
- Comment-embedded hints to the optimizer for selecting an execution plan. See [Database Compatibility for Oracle Developers](/epas/latest/epas_compat_ora_dev_guide/) for information about optimizer hints.
+ Comment-embedded hints to the optimizer for selecting an execution plan. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for information about optimizer hints.
 
 ## FROM clause
 

diff --git a/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx
@@ -19,7 +19,7 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.026.html"
 ---
 
-EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database Compatibility for Oracle Developers](/epas/latest/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server.
+EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server.
 
 ## Enabling compatibility features
 
@@ -38,7 +38,7 @@ EDB Postgres Advanced Server supports a highly productive procedural language th
 -   Provides a seamless development and testing environment.
 -   Allows you to create reusable code.
 
-See [Database Compatibility: Stored Procedural Language](/epas/latest/epas_compat_spl/) for more information.
+See [Stored procedural language](/epas/latest/epas_compat_spl/) for more information.
 
 ## Optimizer hints
 
@@ -123,7 +123,7 @@ For detailed information about the functions supported by the Open Client Librar
 
 ## Utilities
 
-For detailed information about the compatible syntax supported by these utilities, see [Database Compatibility for Oracle Developers: Tools and Utilities](/epas/latest/epas_compat_tools_guide/).
+For detailed information about the compatible syntax supported by these utilities, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/).
 
 ### EDB\*Plus
 
@@ -189,4 +189,4 @@ In a partitioned table, one logically large table is broken into smaller physica
 
 Table partitioning is worthwhile only when a table would otherwise be very large. The exact point at which a table benefits from partitioning depends on the application. A good estimation is when the size of the table exceeds the physical memory of the database server.
 
-For information about database compatibility features supported by EDB Postgres Advanced Server, see [Database Compatibility: Table Partitioning](/epas/latest/epas_compat_table_partitioning/).
+For information about database compatibility features supported by EDB Postgres Advanced Server, see [Table partitioning](/epas/latest/epas_compat_table_partitioning/).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,6 +9,6 @@ legacyRedirectsGenerated:

		<div id="oracle_catalog_views" class="registered_link"></div>

		The Oracle catalog views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is available in [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/).
		The Oracle catalog views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is available in [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,6 +10,6 @@ legacyRedirectsGenerated:

		The system catalog tables contain definitions of database objects that are available to EDB Postgres Advanced Server. The layout of the system tables is subject to change. If you're writing an application that depends on information stored in the system tables, it's prudent to use an existing catalog view or create a catalog view to isolate the application from changes to the system table.

		For detailed information about the system catalog tables, see the [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/).
		For detailed information about the system catalog tables, see the [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -24,4 +24,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 [Database Compatibility for Oracle Developers SQL](/epas/latest/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](/epas/latest/epas_compat_sql/).