From 470d9ea58635142d28281556c372b9d62af51046 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 16 Aug 2022 05:14:34 -0400 Subject: [PATCH 01/32] EPRS: XDB-1592 exclude option requirement --- .../docs/eprs/6.2/eprs_rel_notes/index.mdx | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx index 11c3ba8d5c5..a0da8c9e81e 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx @@ -19,5 +19,32 @@ The EDB Postgres Replication Server documentation describes the latest version o | [6.2.10](19_eprs_rel_notes_6.2.10) | 2020 Jun 11 | | [6.2.9](20_eprs_rel_notes_6.2.9) | 2020 May 07 | +## Installation and upgrade notes +To install Replication Server 6.2.x for the first time or to upgrade to the +latest Replication Server 6.2.x release from an earlier Replication Server 6.2.x release using the EDB repository, you must use the +`--exclude edb-xdb` option with the install or upgrade command. +If the exclude option is not used, Replication Server version 7.0 is +installed. + +To upgrade: + +``` + upgrade ppas-xdb* --exclude edb-xdb* +``` + +To do a fresh install: + +``` + install ppas-xdb --exclude edb-xdb +``` + +Where `` varies by operating system: + +| Package manager | Operating system | +| --------------- | ---------------------------------------- | +| dnf | RHEL 8, OL 8, AlmaLinux 8, Rocky Linux 8 | +| yum | RHEL 7, OL 7, CentOS 7 | +| apt | Debian and Ubuntu | +| zypper | SLES | From 74f216554ac6db1e61ae2c89b5efea58b7050322 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 27 Oct 2022 14:18:07 -0400 Subject: [PATCH 02/32] edits to spl programs section --- .../01_creating_a_procedure.mdx | 63 +++++++++-------- .../02_calling_a_procedure.mdx | 12 ++-- .../03_deleting_a_procedure.mdx | 10 +-- .../04_procedures_overview/index.mdx | 2 +- .../01_creating_a_function.mdx | 69 +++++++++---------- .../02_calling_a_function.mdx | 10 +-- .../03_deleting_a_function.mdx | 10 +-- .../05_functions_overview/index.mdx | 4 +- 8 files changed, 89 insertions(+), 91 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx index 4312551b1f8..ab1a7f4dcd2 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx @@ -4,11 +4,14 @@ title: "Creating a procedure" -The `CREATE PROCEDURE` command defines and names a standalone procedure that are stored in the database. +The `CREATE PROCEDURE` command defines and names a standalone procedure that's stored in the database. -If a schema name is included, then the procedure is created in the specified schema. Otherwise it is created in the current schema. The name of the new procedure must not match any existing procedure with the same input argument types in the same schema. However, procedures of different input argument types may share a name (this is called *overloading*). (Overloading of procedures is an EDB Postgres Advanced Server feature - overloading of stored, standalone procedures is not compatible with Oracle databases.) +If you include a schema name, then the procedure is created in the specified schema. Otherwise it's created in the current schema. The name of the new procedure must not match any existing procedure with the same input argument types in the same schema. However, procedures of different input argument types can share a name. This is called *overloading*. -To update the definition of an existing procedure, use `CREATE OR REPLACE PROCEDURE`. It is not possible to change the name or argument types of a procedure this way (if you tried, you would actually be creating a new, distinct procedure). When using `OUT` parameters, you cannot change the types of any `OUT` parameters except by dropping the procedure. +!!! Note + Overloading of procedures is an EDB Postgres Advanced Server feature. Overloading of stored, standalone procedures isn't compatible with Oracle databases. + +To update the definition of an existing procedure, use `CREATE OR REPLACE PROCEDURE`. You can't change the name or argument types of a procedure this way. Attempting to do so creates a new, distinct procedure. When using `OUT` parameters, you can't change the types of any `OUT` parameters except by dropping the procedure. ```text CREATE [OR REPLACE] PROCEDURE [ () ] @@ -51,11 +54,11 @@ Where: `declarations` - `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. + `declarations` are variable, cursor, type, or subprogram declarations. If you include subprogram declarations, you must declare them after all other variable, cursor, and type declarations. `statements` - `statements` are SPL program statements (the `BEGIN - END` block may contain an `EXCEPTION` section). + `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section. `IMMUTABLE` @@ -63,21 +66,21 @@ Where: `VOLATILE` - These attributes inform the query optimizer about the behavior of the procedure; you can specify only one choice. `VOLATILE` is the default behavior. + These attributes inform the query optimizer about the behavior of the procedure. You can specify only one choice. `VOLATILE` is the default behavior. -- `IMMUTABLE` indicates that the procedure cannot modify the database and always reaches the same result when given the same argument values; it does not do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the procedure with all-constant arguments can be immediately replaced with the procedure value. +- `IMMUTABLE` indicates that the procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups or otherwise use information not directly present in its argument list. If you include this clause, you can immediately replace any call of the procedure with all-constant arguments with the procedure value. -- `STABLE` indicates that the procedure cannot modify the database, and that within a single table scan, it consistently returns the same result for the same argument values, but that its result could change across SQL statements. This is the appropriate selection for procedures that depend on database lookups, parameter variables (such as the current time zone), etc. +- `STABLE` indicates that the procedure can't modify the database. It also indicates that, in a single table scan, it consistently returns the same result for the same argument values but that its result might change across SQL statements. Use this selection for procedures that depend on database lookups, parameter variables (such as the current time zone), and so on. -- `VOLATILE` indicates that the procedure value can change even within a single table scan, so no optimizations can be made. Any function that has side-effects must be classified volatile, even if its result is quite predictable, to prevent calls from being optimized away. +- `VOLATILE` indicates that the procedure value can change even in a single table scan, so you can't make optimizations. You must classify any function that has side effects as volatile, even if its result is predictable, to prevent calls from being optimized away. `DETERMINISTIC` - `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` procedure cannot modify the database and always reaches the same result when given the same argument values; it does not do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the procedure with all-constant arguments can be immediately replaced with the procedure value. + `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the procedure with all-constant arguments can be immediately replaced with the procedure value. `[ NOT ] LEAKPROOF` - A `LEAKPROOF` procedure has no side effects, and reveals no information about the values used to call the procedure. + A `LEAKPROOF` procedure has no side effects and reveals no information about the values used to call the procedure. `CALLED ON NULL INPUT` @@ -85,35 +88,35 @@ Where: `STRICT` -- `CALLED ON NULL INPUT` (the default) indicates that the procedure is called normally when some of its arguments are `NULL`. It is the author's responsibility to check for `NULL` values if necessary and respond appropriately. +- `CALLED ON NULL INPUT` (the default) indicates that the procedure is called normally when some of its arguments are `NULL`. It's the author's responsibility to check for `NULL` values if necessary and respond appropriately. -- `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` whenever any of its arguments are `NULL`. If these clauses are specified, the procedure is not executed when there are `NULL` arguments; instead a `NULL` result is assumed automatically. +- `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` when any of its arguments are `NULL`. If these clauses are specified, the procedure isn't executed when there are `NULL` arguments. Instead a `NULL` result is assumed automatically. `[ EXTERNAL ] SECURITY DEFINER` - `SECURITY DEFINER` specifies for the procedure to execute with the privileges of the user that created it; this is the default. The key word `EXTERNAL` is allowed for SQL conformance, but is optional. + `SECURITY DEFINER` specifies for the procedure to execute with the privileges of the user that created it. This is the default. The key word `EXTERNAL` is allowed for SQL conformance but is optional. `[ EXTERNAL ] SECURITY INVOKER` - The `SECURITY INVOKER` clause indicates for the procedure to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance, but is optional. + The `SECURITY INVOKER` clause indicates for the procedure to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance but is optional. `AUTHID DEFINER` `AUTHID CURRENT_USER` -- The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If the `AUTHID` clause is omitted or if `AUTHID DEFINER` is specified, the rights of the procedure owner are used to determine access privileges to database objects. +- The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If you omit the `AUTHID` clause or specify `AUTHID DEFINER`, the rights of the procedure owner determine access privileges to database objects. -- The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If `AUTHID CURRENT_USER` is specified, the rights of the current user executing the procedure are used to determine access privileges. +- The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If you specify `AUTHID CURRENT_USER`, the rights of the current user executing the procedure determine access privileges. `PARALLEL { UNSAFE | RESTRICTED | SAFE }` - The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query in contrast to a serial sequential scan. + The `PARALLEL` clause enables the use of parallel sequential scans, that is, parallel mode. A parallel sequential scan uses multiple workers to scan a relation in parallel during a query, in contrast to a serial sequential scan. -- When set to `UNSAFE`, the procedure cannot be executed in parallel mode. The presence of such a procedure forces a serial execution plan. This is the default setting if the `PARALLEL` clause is omitted. +- When the value is set to `UNSAFE`, you can't execute the procedure in parallel mode. The presence of such a procedure forces a serial execution plan. This is the default setting. -- When set to `RESTRICTED`, the procedure can be executed in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that is parallel restricted, that relation won't be chosen for parallelism. +- When the value is set to `RESTRICTED`, you can execute the procedure in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that's parallel restricted, that relation isn't chosen for parallelism. -- When set to `SAFE`, the procedure can be executed in parallel mode with no restriction. +- When the value is set to `SAFE`, you can execute the procedure in parallel mode without restriction. `COST execution_cost` @@ -121,26 +124,26 @@ Where: `ROWS result_rows` - `result_rows` is a positive number giving the estimated number of rows that the planner should expect the procedure to return. This is only allowed when the procedure is declared to return a set. The default assumption is 1000 rows. + `result_rows` is a positive number giving the estimated number of rows for the planner to expect the procedure to return. This setting is allowed only when the procedure is declared to return a set. The default is 1000 rows. `SET configuration_parameter { TO value | = value | FROM CURRENT }` - The `SET` clause causes the specified configuration parameter to be set to the specified value when the procedure is entered, and then restored to its prior value when the procedure exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to be applied when the procedure is entered. + The `SET` clause causes the specified configuration parameter to be set to the specified value when the procedure is entered and then restored to its prior value when the procedure exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the procedure is entered. - If a `SET` clause is attached to a procedure, then the effects of a `SET LOCAL` command executed inside the procedure for the same variable are restricted to the procedure; the configuration parameter's prior value is restored at procedure exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, much as it would do for a previous `SET LOCAL` command, with the effects of such a command persisting after procedure exit, unless the current transaction is rolled back. + If a `SET` clause is attached to a procedure, then the effects of a `SET LOCAL` command executed inside the procedure for the same variable are restricted to the procedure. The configuration parameter's prior value is restored at procedure exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, much as it does for a previous `SET LOCAL` command. The effects of this command persist after procedure exit, unless the current transaction is rolled back. `PRAGMA AUTONOMOUS_TRANSACTION` `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the procedure as an autonomous transaction. !!! Note - - The `STRICT, LEAKPROOF, PARALLEL, COST, ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and are not supported by Oracle. + - The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle. - By default, stored procedures are created as `SECURITY DEFINERS`, but when written in plpgsql, the stored procedures are created as `SECURITY INVOKERS`. ## Example -The following is an example of a simple procedure that takes no parameters. +This example shows a simple procedure that takes no parameters: ```text CREATE OR REPLACE PROCEDURE simple_procedure @@ -150,9 +153,9 @@ BEGIN END simple_procedure; ``` -The procedure is stored in the database by entering the procedure code in EDB Postgres Advanced Server. +Store the procedure in the database by entering the procedure code in EDB Postgres Advanced Server. -The following example demonstrates using the `AUTHID DEFINER` and `SET` clauses in a procedure declaration. The `update_salary` procedure conveys the privileges of the role that defined the procedure to the role that is calling the procedure (while the procedure executes): +This example shows using the `AUTHID DEFINER` and `SET` clauses in a procedure declaration. The `update_salary` procedure conveys the privileges of the role that defined the procedure to the role that's calling the procedure while the procedure executes. ```text CREATE OR REPLACE PROCEDURE update_salary(id INT, new_salary NUMBER) @@ -163,6 +166,6 @@ BEGIN END; ``` -Include the `SET` clause to set the procedure's search path to `public` and the work memory to `1MB`. Other procedures, functions and objects aren't affected by these settings. +Include the `SET` clause to set the procedure's search path to `public` and the work memory to `1MB`. These settings don't affect other procedures, functions, and objects. -In this example, the `AUTHID DEFINER` clause temporarily grants privileges to a role that might otherwise not be allowed to execute the statements within the procedure. To instruct the server to use the privileges associated with the role invoking the procedure, replace the `AUTHID DEFINER` clause with the `AUTHID CURRENT_USER` clause. +In the example, the `AUTHID DEFINER` clause temporarily grants privileges to a role that otherwise might not be allowed to execute the statements in the procedure. To instruct the server to use the privileges associated with the role invoking the procedure, replace the `AUTHID DEFINER` clause with the `AUTHID CURRENT_USER` clause. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx index 5c2988a4add..0766eee4110 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx @@ -4,7 +4,7 @@ title: "Calling a procedure" -A procedure can be invoked from another SPL program by simply specifying the procedure name followed by its parameters, if any, followed by a semicolon. +You can invoke a procedure from another SPL program by specifying the procedure name followed by any parameters and a semicolon: ```text [ ([ ]) ]; @@ -14,14 +14,14 @@ Where: `name` is the identifier of the procedure. -`parameters` is a list of actual parameters. +`parameters` is a list of parameters. !!! Note - - If there are no actual parameters to be passed, the procedure may be called with an empty parameter list, or the opening and closing parenthesis may be omitted entirely. + - If there are no parameters to pass, you can call the procedure with an empty parameter list, or you can omit the parentheses. - - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See the *Database Compatibility for Oracle Developers SQL Guide* for information about the `EXEC` command. + - The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [Database Compatibility: SQL](../../../epas_compat_sql/63_exec) for information about the `EXEC` command. -The following is an example of calling the procedure from an anonymous block: +This example calls the procedure from an anonymous block: ```text BEGIN @@ -32,4 +32,4 @@ That's all folks! ``` !!! Note - Each application has its own unique way to call a procedure. For example, in a Java application, the application programming interface, JDBC, is used. + Each application has its own way of calling a procedure. For example, a Java application uses the application programming interface JDBC. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx index 89cfd237f00..581d5dbdc52 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx @@ -4,21 +4,21 @@ title: "Deleting a procedure" -A procedure can be deleted from the database using the `DROP PROCEDURE` command. +You can delete a procedure from the database using the `DROP PROCEDURE` command. ```text DROP PROCEDURE [ IF EXISTS ] [ () ] [ CASCADE | RESTRICT ]; ``` -Where `name` is the name of the procedure to be dropped. +Where `name` is the name of the procedure to drop. !!! Note - - The specification of the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as if this is an overloaded procedure. Oracle requires that the parameter list always be omitted. + - The specification of the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as in an overloaded procedure. Oracle requires that you always omit the parameter list. - - Usage of `IF EXISTS, CASCADE`, or `RESTRICT` is not compatible with Oracle databases. See the `DROP PROCEDURE` command in the *Database Compatibility for Oracle Developers SQL Guide* for information on these options. + - Using `IF EXISTS`, `CASCADE`, or `RESTRICT` isn't compatible with Oracle databases. See [Database Compatibility: SQL](../../../epas_compat_sql/50_drop_procedure) for information on these options. -The previously created procedure is dropped in this example: +This example drops the procedure `simple_procedure`: ```text DROP PROCEDURE simple_procedure; diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx index 5ce0619f5d5..36fc79d833c 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -Procedures are standalone SPL programs that are invoked or called as an individual SPL program statement. When called, procedures may optionally receive values from the caller in the form of input parameters and optionally return values to the caller in the form of output parameters. +Procedures are standalone SPL programs that you invoke or call as an individual SPL program statement. When called, procedures can optionally receive values from the caller in the form of input parameters. They can optionally return values to the caller in the form of output parameters.
diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx index 419d778c8d8..96f9501f40b 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx @@ -6,9 +6,12 @@ title: "Creating a function" The `CREATE FUNCTION` command defines and names a standalone function to store in the database. -If a schema name is included, then the function is created in the specified schema. Otherwise it is created in the current schema. The name of the new function must not match any existing function with the same input argument types in the same schema. However, functions of different input argument types may share a name (this is called *overloading*). (Overloading of functions is an EDB Postgres Advanced Server feature - overloading of stored, standalone functions is not compatible with Oracle databases). +If a schema name is included, then the function is created in the specified schema. Otherwise it's created in the current schema. The name of the new function must not match any existing function with the same input argument types in the same schema. However, functions of different input argument types can share a name. Sharing a name is called *overloading*. -To update the definition of an existing function, use `CREATE OR REPLACE FUNCTION`. It is not possible to change the name or argument types of a function this way (if you tried, you would actually be creating a new, distinct function). Also, `CREATE OR REPLACE FUNCTION` doesn't let you change the return type of an existing function. To do that, you must drop and recreate the function. Also when using `OUT` parameters, you cannot change the types of any `OUT` parameters except by dropping the function. +!!! Note + Overloading functions is an EDB Postgres Advanced Server feature. Overloading stored, standalone functions isn't compatible with Oracle databases. + +To update the definition of an existing function, use `CREATE OR REPLACE FUNCTION`. You can't change the name or argument types of a function this way. If you try to, you instead create a new, distinct function. Also, `CREATE OR REPLACE FUNCTION` doesn't let you change the return type of an existing function. To do that, you must drop and recreate the function. When using `OUT` parameters, you can't change the types of any `OUT` parameters except by dropping the function. ```text CREATE [ OR REPLACE ] FUNCTION [ () ] @@ -42,25 +45,15 @@ CREATE [ OR REPLACE ] FUNCTION [ () ] Where: -`name` - `name` is the identifier of the function. -`parameters` - `parameters` is a list of formal parameters. -`data_type` - `data_type` is the data type of the value returned by the function’s `RETURN` statement. -`declarations` - - `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. - -`statements` + `declarations` are variable, cursor, type, or subprogram declarations. If you include subprogram declarations, you must declare them after all other variable, cursor, and type declarations. - `statements` are SPL program statements (the `BEGIN - END` block may contain an `EXCEPTION` section). + `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section. `IMMUTABLE` @@ -68,21 +61,21 @@ Where: `VOLATILE` - These attributes inform the query optimizer about the behavior of the function; you can specify only one choice. `VOLATILE` is the default behavior. + These attributes inform the query optimizer about the behavior of the function. You can specify only one. `VOLATILE` is the default behavior. -- `IMMUTABLE` indicates that the function cannot modify the database and always reaches the same result when given the same argument values; it does not do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the function with all-constant arguments can be immediately replaced with the function value. +- `IMMUTABLE` indicates that the function can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the function with all-constant arguments can be immediately replaced with the function value. -- `STABLE` indicates that the function cannot modify the database, and that within a single table scan, it consistently returns the same result for the same argument values, but that its result could change across SQL statements. This is the appropriate selection for function that depend on database lookups, parameter variables (such as the current time zone), etc. +- `STABLE` indicates that the function can't modify the database. It also indicates that, in a single table scan, it consistently returns the same result for the same argument values but that its result might change across SQL statements. Select this attribute for functions that depend on database lookups, parameter variables (such as the current time zone), and so on. -- `VOLATILE` indicates that the function value can change even within a single table scan, so no optimizations can be made. Any function that has side-effects must be classified volatile, even if its result is quite predictable, to prevent calls from being optimized away. +- `VOLATILE` indicates that the function value can change even in a single table scan, so no optimizations can be made. Classify any function that has side effects as volatile, even if its result is predictable, to prevent calls from being optimized away. `DETERMINISTIC` - `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` function cannot modify the database and always reaches the same result when given the same argument values; it does not do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the function with all-constant arguments can be immediately replaced with the function value. + `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` function can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, you can replace any call of the function with all-constant arguments with the function value. `[ NOT ] LEAKPROOF` - A `LEAKPROOF` function has no side effects, and reveals no information about the values used to call the function. + A `LEAKPROOF` function has no side effects and reveals no information about the values used to call the function. `CALLED ON NULL INPUT` @@ -92,33 +85,33 @@ Where: - `CALLED ON NULL INPUT` (the default) indicates for the procedure to be called normally when some of its arguments are `NULL`. It is the author's responsibility to check for `NULL` values if necessary and respond appropriately. -- `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` whenever any of its arguments are `NULL`. If these clauses are specified, the procedure is not executed when there are `NULL` arguments; instead a `NULL` result is assumed automatically. +- `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` when any of its arguments are `NULL`. If you specify these clauses, the procedure isn't executed when there are `NULL` arguments. Instead, a `NULL` result is assumed automatically. `[ EXTERNAL ] SECURITY DEFINER` - `SECURITY DEFINER` specifies for the function to execute with the privileges of the user that created it; this is the default. The key word `EXTERNAL` is allowed for SQL conformance, but is optional. + `SECURITY DEFINER` (the default) specifies for the function to execute with the privileges of the user that created it. The key word `EXTERNAL` is allowed for SQL conformance but is optional. `[ EXTERNAL ] SECURITY INVOKER` - The `SECURITY INVOKER` clause indicates for the function to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance, but is optional. + The `SECURITY INVOKER` clause indicates for the function to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance but is optional. `AUTHID DEFINER` `AUTHID CURRENT_USER` -- The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If the `AUTHID` clause is omitted or if `AUTHID DEFINER` is specified, the rights of the function owner are used to determine access privileges to database objects. +- The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If the `AUTHID` clause is omitted or if `AUTHID DEFINER` is specified, the rights of the function owner determine access privileges to database objects. -- The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If `AUTHID CURRENT_USER` is specified, the rights of the current user executing the function are used to determine access privileges. +- The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If `AUTHID CURRENT_USER` is specified, the rights of the current user executing the function determine access privileges. `PARALLEL { UNSAFE | RESTRICTED | SAFE }` - The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query in contrast to a serial sequential scan. + The `PARALLEL` clause enables the use of parallel sequential scans, that is, parallel mode. A parallel sequential scan uses multiple workers to scan a relation in parallel during a query in contrast to a serial sequential scan. -- When set to `UNSAFE`, the function cannot be executed in parallel mode. The presence of such a function in a SQL statement forces a serial execution plan. This is the default setting if the `PARALLEL` clause is omitted. +- When this value is set to `UNSAFE`, you can't execute the function in parallel mode. The presence of such a function in a SQL statement forces a serial execution plan. This is the default setting. -- When set to `RESTRICTED`, the function can be executed in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that is parallel restricted, that relation won't be chosen for parallelism. +- When this value is set to `RESTRICTED`, you can execute the function in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that's parallel restricted, that relation isn't chosen for parallelism. -- When set to `SAFE`, the function can be executed in parallel mode with no restriction. +- When this value is set to `SAFE`, you can execute the function in parallel mode with no restriction. `COST execution_cost` @@ -126,24 +119,24 @@ Where: `ROWS result_rows` - `result_rows` is a positive number giving the estimated number of rows that the planner should expect the function to return. This is only allowed when the function is declared to return a set. The default assumption is 1000 rows. + `result_rows` is a positive number giving the estimated number of rows for the planner to expect the function to return. This is allowed only when the function is declared to return a set. The default assumption is 1000 rows. `SET configuration_parameter { TO value | = value | FROM CURRENT }` - The `SET` clause causes the specified configuration parameter to be set to the specified value when the function is entered, and then restored to its prior value when the function exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to be applied when the function is entered. + The `SET` clause causes the specified configuration parameter to be set to the specified value when the function is entered and then restored to its prior value when the function exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the function is entered. - If a `SET` clause is attached to a function, then the effects of a `SET LOCAL` command executed inside the function for the same variable are restricted to the function; the configuration parameter's prior value is restored at function exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, much as it would do for a previous `SET LOCAL` command, with the effects of such a command persisting after procedure exit, unless the current transaction is rolled back. + If a `SET` clause is attached to a function, then the effects of a `SET LOCAL` command executed inside the function for the same variable are restricted to the function. The configuration parameter's prior value is restored at function exit. A `SET` command without `LOCAL` overrides the `SET` clause, much as it does for a previous `SET LOCAL` command. The effects of such a command persist after procedure exit, unless the current transaction is rolled back. `PRAGMA AUTONOMOUS_TRANSACTION` `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the function as an autonomous transaction. !!! Note - The `STRICT, LEAKPROOF, PARALLEL, COST, ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and are not supported by Oracle. + The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle. ## Examples -The following is an example of a simple function that takes no parameters. +This example shows a simple function that takes no parameters: ```text CREATE OR REPLACE FUNCTION simple_function @@ -154,7 +147,7 @@ BEGIN END simple_function; ``` -The following function takes two input parameters. Parameters are discussed in more detail in subsequent sections. +This function takes two input parameters: ```text CREATE OR REPLACE FUNCTION emp_comp ( @@ -167,7 +160,7 @@ BEGIN END emp_comp; ``` -The following example demonstrates using the `AUTHID CURRENT_USER` clause and `STRICT` keyword in a function declaration: +This example uses the `AUTHID CURRENT_USER` clause and `STRICT` keyword in a function declaration: ```text CREATE OR REPLACE FUNCTION dept_salaries(dept_id int) RETURN NUMBER @@ -178,6 +171,6 @@ BEGIN END; ``` -Include the `STRICT` keyword to instruct the server to return `NULL` if any input parameter passed is `NULL`; if a `NULL` value is passed, the function doesn't execute. +Include the `STRICT` keyword to instruct the server to return `NULL` if any input parameter passed is `NULL`. If a `NULL` value is passed, the function doesn't execute. -The `dept_salaries` function executes with the privileges of the role that is calling the function. If the current user does not have sufficient privileges to perform the `SELECT` statement querying the `emp` table (to display employee salaries), the function reports an error. To instruct the server to use the privileges associated with the role that defined the function, replace the `AUTHID CURRENT_USER` clause with the `AUTHID DEFINER` clause. +The `dept_salaries` function executes with the privileges of the role that's calling the function. If the current user doesn't have the privileges to perform the `SELECT` statement querying the `emp` table (to display employee salaries), the function reports an error. To instruct the server to use the privileges associated with the role that defined the function, replace the `AUTHID CURRENT_USER` clause with the `AUTHID DEFINER` clause. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx index 5d94b9cdbbe..df12fe4cc2c 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx @@ -4,7 +4,7 @@ title: "Calling a function" -A function can be used anywhere an expression can appear within an SPL statement. A function is invoked by simply specifying its name followed by its parameters enclosed in parenthesis, if any. +You can use a function anywhere an expression can appear in an SPL statement. Invoke a function by specifying its name followed by any parameters enclosed in parentheses. ```text [ ([ ]) ] @@ -12,12 +12,12 @@ A function can be used anywhere an expression can appear within an SPL statement `name` is the name of the function. -`parameters` is a list of actual parameters. +`parameters` is a list of parameters. !!! Note - If there are no actual parameters to be passed, the function may be called with an empty parameter list, or the opening and closing parenthesis may be omitted entirely. + If there are no parameters to pass, you can call the function with an empty parameter list, or you can omit the parentheses. -The following shows how the function can be called from another SPL program. +This example shows how to call the function from another SPL program: ```text BEGIN @@ -27,7 +27,7 @@ END; That's All Folks! ``` -A function is typically used within a SQL statement as shown in the following. +You typically use a function in a SQL statement, as this example shows: ```text SELECT empno "EMPNO", ename "ENAME", sal "SAL", comm "COMM", diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx index 47baaa8842e..4bb27178cc3 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx @@ -4,21 +4,21 @@ title: "Deleting a function" -A function can be deleted from the database using the `DROP FUNCTION` command. +You can delete a function from the database using `DROP FUNCTION`. ```text DROP FUNCTION [ IF EXISTS ] [ () ] [ CASCADE | RESTRICT ]; ``` -Where `name` is the name of the function to be dropped. +Where `name` is the name of the function to drop. !!! Note - - The specification of the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as if this is an overloaded function. Oracle requires that the parameter list always be omitted. + - Specifying the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as in an overloaded function. Oracle requires that you always omit the parameter list. - - Usage of `IF EXISTS, CASCADE`, or `RESTRICT` is not compatible with Oracle databases. See the `DROP FUNCTION` command in the *Database Compatibility for Oracle Developers SQL Guide* for information on these options. + - Use of `IF EXISTS`, `CASCADE`, or `RESTRICT` isn't compatible with Oracle databases. See the [Database Compatibility: SQL](../../../epas_compat_sql/47_drop_function) for information on these options. -The previously created function is dropped in this example: +This example drops the function `simple_function`: ```text DROP FUNCTION simple_function; diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx index 52c42742c92..42aef9613e7 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx @@ -8,7 +8,9 @@ legacyRedirectsGenerated: -Functions are standalone SPL programs that are invoked as expressions. When evaluated, a function returns a value that is substituted in the expression in which the function is embedded. Functions may optionally take values from the calling program in the form of input parameters. In addition to the fact that the function, itself, returns a value, a function may optionally return additional values to the caller in the form of output parameters. The use of output parameters in functions, however, is not an encouraged programming practice. +Functions are standalone SPL programs that are invoked as expressions. When evaluated, a function returns a value that's substituted in the expression in which the function is embedded. Functions can optionally take values from the calling program in the form of input parameters. + +In addition to the fact that the function returns a value, a function can also optionally return values to the caller in the form of output parameters. However, we don't encourage the use of output parameters in functions.
From 72409e8e4c1282f5deea8b2200a0de98ed991c19 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 10 Nov 2022 13:59:25 -0500 Subject: [PATCH 03/32] change to one file --- .../01_positional_vs_named_parameter_notation.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx index 04b8886d359..ac025dd115e 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx @@ -4,11 +4,11 @@ title: "Positional versus named parameter notation" -You can use either *positional* or *named* parameter notation when passing parameters to a function or procedure. If you specify parameters using positional notation, you must list the parameters in the order that they are declared; if you specify parameters with named notation, the order of the parameters is not significant. +You can use either *positional* or *named* parameter notation when passing parameters to a function or procedure. If you specify parameters using positional notation, you must list the parameters in the order that they are declared. If you specify parameters with named notation, the order of the parameters doesn't matter. -To specify parameters using named notation, list the name of each parameter followed by an arrow `(=>)` and the parameter value. Named notation is more verbose, but makes your code easier to read and maintain. +To specify parameters using named notation, list the name of each parameter followed by an arrow (`=>`) and the parameter value. Named notation is more verbose but makes your code easier to read and maintain. -A simple example that demonstrates using positional and named parameter notation follows: +This example uses positional and named parameter notation: ```text CREATE OR REPLACE PROCEDURE emp_info ( @@ -36,9 +36,9 @@ To call the procedure using named notation, pass the following: emp_info(p_ename =>'Clark', p_empno=>7455, p_deptno=>30); ``` -Using named notation can alleviate the need to re-arrange a procedure’s parameter list if the parameter list changes, if the parameters are reordered or if a new optional parameter is added. +If you used named notation, you don't need to rearrange a procedure’s parameter list if the parameter list changes, the parameters are reordered, or a new, optional parameter is added. -In a case where you have a default value for an argument and the argument is not a trailing argument, you must use named notation to call the procedure or function. The following case demonstrates a procedure with two, leading, default arguments. +When you have a default value for an argument and the argument isn't a trailing argument, you must use named notation to call the procedure or function. The following case demonstrates a procedure with two leading, default arguments. ```text CREATE OR REPLACE PROCEDURE check_balance ( From 1d11c03c596eb09f55f3b1dba848a2c80f3e8a09 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 10 Nov 2022 15:45:21 -0500 Subject: [PATCH 04/32] first read-through of procedure and function parameters --- ...positional_vs_named_parameter_notation.mdx | 8 ++++---- .../02_parameter_modes.mdx | 10 +++++----- .../03_using_default_values_in_parameters.mdx | 10 ++++------ .../index.mdx | 19 +++++++++++-------- 4 files changed, 24 insertions(+), 23 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx index ac025dd115e..f0fc180f34d 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx @@ -38,7 +38,7 @@ emp_info(p_ename =>'Clark', p_empno=>7455, p_deptno=>30); If you used named notation, you don't need to rearrange a procedure’s parameter list if the parameter list changes, the parameters are reordered, or a new, optional parameter is added. -When you have a default value for an argument and the argument isn't a trailing argument, you must use named notation to call the procedure or function. The following case demonstrates a procedure with two leading, default arguments. +When an argument has a default value and the argument isn't a trailing argument, you must use named notation to call the procedure or function. This example shows a procedure with two leading default arguments. ```text CREATE OR REPLACE PROCEDURE check_balance ( @@ -69,7 +69,7 @@ BEGIN END; ``` -You can only omit non-trailing argument values (when you call this procedure) by using named notation; when using positional notation, only trailing arguments are allowed to default. You can call this procedure with the following arguments: +You can omit nontrailing argument values (when you call this procedure) only by using named notation. When using positional notation, only trailing arguments are allowed to default. You can call this procedure with the following arguments: ``` check_balance(p_customerID => 10, p_amount = 500.00) @@ -77,7 +77,7 @@ check_balance(p_customerID => 10, p_amount = 500.00) check_balance(p_balance => 1000.00, p_amount = 500.00) ``` -You can use a combination of positional and named notation (mixed notation) to specify parameters. A simple example that demonstrates using mixed parameter notation follows: +You can use a combination of positional and named notation (*mixed* notation) to specify parameters. This example shows using mixed parameter notation: ```text CREATE OR REPLACE PROCEDURE emp_info ( @@ -99,4 +99,4 @@ You can call the procedure using mixed notation: emp_info(30, p_ename =>'Clark', p_empno=>7455); ``` -If you do use mixed notation, remember that named arguments cannot precede positional arguments. +If you use mixed notation, remember that named arguments can't precede positional arguments. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx index 74bd3cf0702..c4e28538e7e 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx @@ -4,12 +4,12 @@ title: "Parameter modes" -As previously discussed, a parameter has one of three possible modes - `IN, OUT`, or `IN OUT`. The following characteristics of a formal parameter are dependent upon its mode: +A parameter has one of three possible modes: `IN`, `OUT`, or `IN OUT`. The following characteristics of a formal parameter depend upon its mode: -- Its initial value when the procedure or function is called. -- Whether or not the called procedure or function can modify the formal parameter. -- How the actual parameter value is passed from the calling program to the called program. -- What happens to the formal parameter value when an unhandled exception occurs in the called program. +- Its initial value when the procedure or function is called +- Whether the called procedure or function can modify the formal parameter +- How the actual parameter value is passed from the calling program to the called program +- What happens to the formal parameter value when an unhandled exception occurs in the called program The following table summarizes the behavior of parameters according to their mode. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx index 96ccbf3f9cd..f48a982e814 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx @@ -4,7 +4,7 @@ title: "Using default values in parameters" -You can set a default value of a formal parameter by including the `DEFAULT` clause or using the assignment operator `(:=)` in the `CREATE PROCEDURE` or `CREATE FUNCTION` statement. +You can set a default value of a formal parameter by including the `DEFAULT` clause or using the assignment operator (`:=`) in the `CREATE PROCEDURE` or `CREATE FUNCTION` statement. The general form of a formal parameter declaration is: @@ -20,9 +20,9 @@ The general form of a formal parameter declaration is: `expr` is the default value assigned to the parameter. If you don't include a `DEFAULT` clause, the caller must provide a value for the parameter. -The default value is evaluated every time the function or procedure is invoked. For example, assigning `SYSDATE` to a parameter of type `DATE` causes the parameter to have the time of the current invocation, not the time when the procedure or function was created. +The default value is evaluated every time you invoke the function or procedure. For example, assigning `SYSDATE` to a parameter of type `DATE` causes the parameter to have the time of the current invocation, not the time when the procedure or function was created. -The following simple procedure demonstrates using the assignment operator to set a default value of `SYSDATE` into the parameter, `hiredate:` +This example uses the assignment operator to set a default value of `SYSDATE` into the parameter `hiredate:` ```text CREATE OR REPLACE PROCEDURE hire_emp ( @@ -45,14 +45,12 @@ If the parameter declaration includes a default value, you can omit the paramete hire_emp (7575, Clark) ``` -If you do include a value for the actual parameter when you call the procedure, that value takes precedence over the default value: +If you do include a value for the actual parameter when you call the procedure, that value takes precedence over the default value. This command adds a new employee with a hiredate of `February 15, 2010`, regardless of the current value of `SYSDATE`. ```text hire_emp (7575, Clark, 15-FEB-2010) ``` -Adds a new employee with a hiredate of `February 15, 2010`, regardless of the current value of `SYSDATE`. - You can write the same procedure by substituting the `DEFAULT` keyword for the assignment operator: ```text diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx index ada0f9a53ed..ecb3d1bf21c 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx @@ -8,9 +8,9 @@ legacyRedirectsGenerated: -An important aspect of using procedures and functions is the capability to pass data from the calling program to the procedure or function and to receive data back from the procedure or function. This is accomplished by using *parameters*. +An important aspect of using procedures and functions is the capability to pass data from the calling program to the procedure or function and to receive data back from the procedure or function. You do this by using *parameters*. -Parameters are declared in the procedure or function definition, enclosed within parenthesis following the procedure or function name. Parameters declared in the procedure or function definition are known as *formal parameters*. When the procedure or function is invoked, the calling program supplies the actual data that is to be used in the called program’s processing as well as the variables that are to receive the results of the called program’s processing. The data and variables supplied by the calling program when the procedure or function is called are referred to as the *actual parameters*. +Declare parameters in the procedure or function definition, and enclose them in parentheses following the procedure or function name. Parameters declared in the procedure or function definition are known as *formal parameters*. When you invoke the procedure or function, the calling program supplies the actual data to use in the called program’s processing as well as the variables that receive the results of the called program’s processing. The data and variables supplied by the calling program when the procedure or function is called are referred to as the *actual parameters*. The following is the general format of a formal parameter declaration. @@ -18,9 +18,12 @@ The following is the general format of a formal parameter declaration. ( [ IN | OUT | IN OUT ] [ DEFAULT ]) ``` -`name` is an identifier assigned to the formal parameter. If specified, `IN` defines the parameter for receiving input data into the procedure or function. An `IN` parameter can also be initialized to a default value. If specified, `OUT` defines the parameter for returning data from the procedure or function. If specified, `IN OUT` allows the parameter to be used for both input and output. If all of `IN, OUT`, and `IN OUT` are omitted, then the parameter acts as if it were defined as `IN` by default. Whether a parameter is `IN, OUT`, or `IN OUT` is referred to as the parameter’s *mode*. `data_type` defines the data type of the parameter. `value` is a default value assigned to an `IN` parameter in the called program if an actual parameter is not specified in the call. +- `name` is an identifier assigned to the formal parameter. +- If specified, `IN` defines the parameter for receiving input data into the procedure or function. An `IN` parameter can also be initialized to a default value. If specified, `OUT` defines the parameter for returning data from the procedure or function. If specified, `IN OUT` allows the parameter to be used for both input and output. If all of `IN`, `OUT`, and `IN OUT` are omitted, then the parameter acts as if it were defined as `IN` by default. Whether a parameter is `IN`, `OUT`, or `IN OUT` is referred to as the parameter’s *mode*. +- `data_type` defines the data type of the parameter. +- `value` is a default value assigned to an `IN` parameter in the called program if an actual parameter isn't specified in the call. -The following is an example of a procedure that takes parameters: +This example shows a procedure that takes parameters: ```text CREATE OR REPLACE PROCEDURE emp_query ( @@ -45,9 +48,9 @@ END; In this example, `p_deptno` is an `IN` formal parameter, `p_empno` and `p_ename` are `IN OUT` formal parameters, and `p_job, p_hiredate`, and `p_sal` are `OUT` formal parameters. !!! Note - In the previous example, no maximum length was specified on the `VARCHAR2` parameters and no precision and scale were specified on the `NUMBER` parameters. It is illegal to specify a length, precision, scale or other constraints on parameter declarations. These constraints are automatically inherited from the actual parameters that are used when the procedure or function is called. + In the example, no maximum length was specified on the `VARCHAR2` parameters and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are automatically inherited from the actual parameters that are used when the procedure or function is called. -The `emp_query` procedure can be called by another program, passing it the actual parameters. The following is an example of another SPL program that calls `emp_query`. +The `emp_query` procedure can be called by another program, passing it the actual parameters. This example is another SPL program that calls `emp_query`. ```text DECLARE @@ -71,9 +74,9 @@ BEGIN END; ``` -In this example, `v_deptno, v_empno, v_ename, v_job, v_hiredate`, and `v_sal` are the actual parameters. +In this example, `v_deptno`, `v_empno`, `v_ename`, `v_job`, `v_hiredate`, and `v_sal` are the actual parameters. -The output from the preceding example is shown as follows: +The output from the preceding example is: ```text Department : 30 From 8c439982aa7a37f58bd362331e3c74bd3bf1fd45 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 15 Nov 2022 13:18:13 -0500 Subject: [PATCH 05/32] first read of subprograms section --- ...positional_vs_named_parameter_notation.mdx | 10 +-- .../02_parameter_modes.mdx | 8 +-- .../03_using_default_values_in_parameters.mdx | 2 +- .../index.mdx | 10 +-- .../01_creating_a_subprocedure.mdx | 28 +++----- .../02_creating_a_subfunction.mdx | 28 +++----- .../03_block_relationships.mdx | 16 ++--- .../04_invoking_subprograms.mdx | 68 +++++++++---------- .../05_using_forward_declarations.mdx | 12 ++-- .../06_overloading_subprograms.mdx | 34 +++++----- .../07_accessing_subprogram_variables.mdx | 48 ++++++------- .../index.mdx | 13 ++-- 12 files changed, 126 insertions(+), 151 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx index f0fc180f34d..43389136184 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx @@ -36,9 +36,9 @@ To call the procedure using named notation, pass the following: emp_info(p_ename =>'Clark', p_empno=>7455, p_deptno=>30); ``` -If you used named notation, you don't need to rearrange a procedure’s parameter list if the parameter list changes, the parameters are reordered, or a new, optional parameter is added. +If you used named notation, you don't need to rearrange a procedure’s parameter list if the parameter list changes, the parameters are reordered, or an optional parameter is added. -When an argument has a default value and the argument isn't a trailing argument, you must use named notation to call the procedure or function. This example shows a procedure with two leading default arguments. +When an argument has a default value and the argument isn't a trailing argument, you must use named notation to call the procedure or function. This example shows a procedure with two leading default arguments: ```text CREATE OR REPLACE PROCEDURE check_balance ( @@ -69,7 +69,7 @@ BEGIN END; ``` -You can omit nontrailing argument values (when you call this procedure) only by using named notation. When using positional notation, only trailing arguments are allowed to default. You can call this procedure with the following arguments: +You can omit nontrailing argument values when you call this procedure only by using named notation. When using positional notation, only trailing arguments are allowed to default. You can call this procedure with the following arguments: ``` check_balance(p_customerID => 10, p_amount = 500.00) @@ -77,7 +77,7 @@ check_balance(p_customerID => 10, p_amount = 500.00) check_balance(p_balance => 1000.00, p_amount = 500.00) ``` -You can use a combination of positional and named notation (*mixed* notation) to specify parameters. This example shows using mixed parameter notation: +You can use a combination of positional and named notation, referred to as *mixed* notation, to specify parameters. This example shows using mixed parameter notation: ```text CREATE OR REPLACE PROCEDURE emp_info ( @@ -99,4 +99,4 @@ You can call the procedure using mixed notation: emp_info(30, p_ename =>'Clark', p_empno=>7455); ``` -If you use mixed notation, remember that named arguments can't precede positional arguments. +When using mixed notation, named arguments can't precede positional arguments. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx index c4e28538e7e..02b10124b0f 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx @@ -4,7 +4,7 @@ title: "Parameter modes" -A parameter has one of three possible modes: `IN`, `OUT`, or `IN OUT`. The following characteristics of a formal parameter depend upon its mode: +A parameter has one of three possible modes: `IN`, `OUT`, or `IN OUT`. The following characteristics of a formal parameter depend on its mode: - Its initial value when the procedure or function is called - Whether the called procedure or function can modify the formal parameter @@ -21,8 +21,8 @@ The following table summarizes the behavior of parameters according to their mod | Actual parameter contains: (after a handled exception in the called program) | Original actual parameter value prior to the call | Last value of the formal parameter | Last value of the formal parameter | | Actual parameter contains: (after an unhandled exception in the called program) | Original actual parameter value prior to the call | Original actual parameter value prior to the call | Original actual parameter value prior to the call | -As shown by the table, an `IN` formal parameter is initialized to the actual parameter with which it is called unless it was explicitly initialized with a default value. The `IN` parameter may be referenced within the called program, however, the called program may not assign a new value to the `IN` parameter. After control returns to the calling program, the actual parameter always contains the same value as it was set to prior to the call. +As shown by the table, an `IN` formal parameter is initialized to the actual parameter with which it's called unless it was explicitly initialized with a default value. You can reference the `IN` parameter in the called program. However, the called program can't assign a new value to the `IN` parameter. After control returns to the calling program, the actual parameter always contains the same value that it had prior to the call. -The `OUT` formal parameter is initialized to the actual parameter with which it is called. The called program may reference and assign new values to the formal parameter. If the called program terminates without an exception, the actual parameter takes on the value last set in the formal parameter. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call. +The `OUT` formal parameter is initialized to the actual parameter with which it's called. The called program can reference and assign new values to the formal parameter. If the called program ends without an exception, the actual parameter takes on the value last set in the formal parameter. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call. -Like an `IN` parameter, an `IN OUT` formal parameter is initialized to the actual parameter with which it is called. Like an `OUT` parameter, an `IN OUT` formal parameter is modifiable by the called program and the last value in the formal parameter is passed to the calling program’s actual parameter if the called program terminates without an exception. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call. +Like an `IN` parameter, an `IN OUT` formal parameter is initialized to the actual parameter with which it's called. Like an `OUT` parameter, an `IN OUT` formal parameter can be modifiwed by the called program. The last value in the formal parameter is passed to the calling program’s actual parameter if the called program ends without an exception. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx index f48a982e814..d6b5e832da4 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx @@ -45,7 +45,7 @@ If the parameter declaration includes a default value, you can omit the paramete hire_emp (7575, Clark) ``` -If you do include a value for the actual parameter when you call the procedure, that value takes precedence over the default value. This command adds a new employee with a hiredate of `February 15, 2010`, regardless of the current value of `SYSDATE`. +If you do include a value for the actual parameter when you call the procedure, that value takes precedence over the default value. This command adds an employee with a hiredate of `February 15, 2010`, regardless of the current value of `SYSDATE`. ```text hire_emp (7575, Clark, 15-FEB-2010) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx index ecb3d1bf21c..b1c3ca92907 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx @@ -19,9 +19,9 @@ The following is the general format of a formal parameter declaration. ``` - `name` is an identifier assigned to the formal parameter. -- If specified, `IN` defines the parameter for receiving input data into the procedure or function. An `IN` parameter can also be initialized to a default value. If specified, `OUT` defines the parameter for returning data from the procedure or function. If specified, `IN OUT` allows the parameter to be used for both input and output. If all of `IN`, `OUT`, and `IN OUT` are omitted, then the parameter acts as if it were defined as `IN` by default. Whether a parameter is `IN`, `OUT`, or `IN OUT` is referred to as the parameter’s *mode*. +- Whether a parameter is `IN`, `OUT`, or `IN OUT` is referred to as the parameter’s *mode*. If specified, `IN` defines the parameter for receiving input data into the procedure or function. An `IN` parameter can also be initialized to a default value. If specified, `OUT` defines the parameter for returning data from the procedure or function. If specified, `IN OUT` allows the parameter to be used for both input and output. If all of `IN`, `OUT`, and `IN OUT` are omitted, then the parameter acts as if it were defined as `IN` by default. - `data_type` defines the data type of the parameter. -- `value` is a default value assigned to an `IN` parameter in the called program if an actual parameter isn't specified in the call. +- `value` is a default value assigned to an `IN` parameter in the called program if you don't specify an actual parameter in the call. This example shows a procedure that takes parameters: @@ -45,10 +45,10 @@ BEGIN END; ``` -In this example, `p_deptno` is an `IN` formal parameter, `p_empno` and `p_ename` are `IN OUT` formal parameters, and `p_job, p_hiredate`, and `p_sal` are `OUT` formal parameters. +In this example, `p_deptno` is an `IN` formal parameter, `p_empno` and `p_ename` are `IN OUT` formal parameters, and `p_job, p_hiredate` and `p_sal` are `OUT` formal parameters. !!! Note - In the example, no maximum length was specified on the `VARCHAR2` parameters and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are automatically inherited from the actual parameters that are used when the procedure or function is called. + In the example, no maximum length was specified on the `VARCHAR2` parameters and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are inherited from the actual parameters that are used when the procedure or function is called. The `emp_query` procedure can be called by another program, passing it the actual parameters. This example is another SPL program that calls `emp_query`. @@ -76,7 +76,7 @@ END; In this example, `v_deptno`, `v_empno`, `v_ename`, `v_job`, `v_hiredate`, and `v_sal` are the actual parameters. -The output from the preceding example is: +The output from the example is: ```text Department : 30 diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx index e1bf6a47370..45fb44b76dd 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx @@ -8,9 +8,9 @@ The `PROCEDURE` clause specified in the declaration section defines and names a The term *block* refers to the SPL block structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks are the structures for standalone procedures and functions, anonymous blocks, subprograms, triggers, packages, and object type methods. -The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared within the declaration section of that block and is therefore accessible by the SPL code within the executable section and optional exception section of that block. +The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block and is therefore the SPL code can access it in the executable section and optional exception section of that block. -Subprocedures can only be declared after all other variable, cursor, and type declarations included in the declaration section. (That is, subprograms must be the last set of declarations.) +You can declare subprocedures only after all the other variable, cursor, and type declarations included in the declaration section. Subprograms must be the last set of declarations. ```text PROCEDURE [ () ] @@ -24,29 +24,19 @@ PROCEDURE [ () ] Where: -`name` +- `name` is the identifier of the subprocedure. - `name` is the identifier of the subprocedure. +- `parameters` is a list of formal parameters. -`parameters` +- `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subprocedure as an autonomous transaction. - `parameters` is a list of formal parameters. +- `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, you must declare them after all other variable, cursor, and type declarations. -`PRAGMA AUTONOMOUS_TRANSACTION` - - `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subprocedure as an autonomous transaction. - -`declarations` - - `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. - -`statements` - - `statements` are SPL program statements (the `BEGIN - END` block may contain an `EXCEPTION` section). +- `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section. ## Examples -The following example is a subprocedure within an anonymous block. +This example is a subprocedure in an anonymous block: ```text DECLARE @@ -95,7 +85,7 @@ EMPNO ENAME 7934 MILLER ``` -The following example is a subprocedure within a trigger. +This example is a subprocedure in a trigger: ```text CREATE OR REPLACE TRIGGER dept_audit_trig diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx index 65fd0efbef6..976d92bfd6a 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx @@ -8,7 +8,7 @@ The `FUNCTION` clause specified in the declaration section defines and names a s The term *block* refers to the SPL block structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks are the structures for standalone procedures and functions, anonymous blocks, subprograms, triggers, packages, and object type methods. -The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared within the declaration section of that block and is therefore accessible by the SPL code within the executable section and optional exception section of that block. +The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block and is therefore accessible by the SPL code in the executable section and optional exception section of that block. ```text FUNCTION [ () ] @@ -23,29 +23,17 @@ RETURN Where: -`name` +- `name` is the identifier of the subfunction. - `name` is the identifier of the subfunction. +- `parameters` is a list of formal parameters. -`parameters` +- `data_type` is the data type of the value returned by the function’s `RETURN` statement. - `parameters` is a list of formal parameters. +- `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subfunction as an autonomous transaction. -`data_type` +- `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. - `data_type` is the data type of the value returned by the function’s `RETURN` statement. - -`PRAGMA AUTONOMOUS_TRANSACTION` - - `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subfunction as an autonomous transaction. - -`declarations` - - `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. - -`statements` - - `statements` are SPL program statements (the `BEGIN - END` block may contain an `EXCEPTION` section). +- `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section. ## Examples @@ -71,7 +59,7 @@ BEGIN END; ``` -The output from the example is the following: +The following is the output: ```text 1! = 1 diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx index 03b078ea693..07320f03c07 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx @@ -4,24 +4,24 @@ title: "Block relationships" -This section describes the terminology of the relationship between blocks that can be declared in an SPL program. The ability to invoke subprograms and access identifiers declared within a block depends upon this relationship. +You can declare the relationship between blocks in an SPL program. The ability to invoke subprograms and access identifiers declared in a block depends upon this relationship. The following are the basic terms: - A *block* is the basic SPL structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks implement standalone procedure and function programs, anonymous blocks, triggers, packages, and subprocedures and subfunctions. -- An identifier (variable, cursor, type, or subprogram) *local to a block* means that it is declared within the declaration section of the given block. Such local identifiers are accessible from the executable section and optional exception section of the block. -- The *parent block* contains the declaration of another block (the *child block*). +- An identifier (variable, cursor, type, or subprogram) *local to a block* means that it's declared in the declaration section of the given block. Such local identifiers are accessible from the executable section and optional exception section of the block. +- The *parent block* contains the declaration of another block, that is, the *child block*. - *Descendent blocks* are the set of blocks forming the child relationship starting from a given parent block. - *Ancestor blocks* are the set of blocks forming the parental relationship starting from a given child block. -- The set of descendent (or ancestor) blocks form a *hierarchy*. -- The *level* is an ordinal number of a given block from the highest, ancestor block. For example, given a standalone procedure, the subprograms declared within the declaration section of this procedure are all at the same level, for example call it level 1. Additional subprograms within the declaration section of the subprograms declared in the standalone procedure are at the next level, which is level 2. -- The *sibling blocks* are the set of blocks that have the same parent block (that is, they are all locally declared in the same block). Sibling blocks are also always at the same level relative to each other. +- The set of descendent (ancestor) blocks form a *hierarchy*. +- The *level* is an ordinal number of a given block from the highest, ancestor block. For example, given a standalone procedure, the subprograms declared in the declaration section of this procedure are all at the same level, for example, level 1. Additional subprograms in the declaration section of the subprograms declared in the standalone procedure are at the next level, that is, level 2. +- The *sibling blocks* are the set of blocks that have the same parent block,that is, they are all locally declared in the same block. Sibling blocks are always at the same level relative to each other. The following schematic of a set of procedure declaration sections provides an example of a set of blocks and their relationships to their surrounding blocks. The two vertical lines on the left-hand side of the blocks indicate there are two pairs of sibling blocks. `block_1a` and `block_1b` is one pair, and `block_2a` and `block_2b` is the second pair. -The relationship of each block with its ancestors is shown on the right-hand side of the blocks. There are three hierarchical paths formed when progressing up the hierarchy from the lowest level child blocks. The first consists of `block_0, block_1a, block_2a`, and `block_3`. The second is `block_0, block_1a`, and `block_2b`. The third is `block_0, block_1b`, and `block_2b`. +The relationship of each block with its ancestors is shown on the right-hand side of the blocks. Three hierarchical paths are formed when progressing up the hierarchy from the lowest level child blocks. The first consists of `block_0`, `block_1a`, `block_2a`, and `block_3`. The second is `block_0`, `block_1a`, and `block_2b`. The third is `block_0`, `block_1b`, and `block_2b`. ```text CREATE PROCEDURE block_0 @@ -72,4 +72,4 @@ BEGIN END block_0; ``` -The rules for invoking subprograms based upon block location is described starting with [Invoking Subprograms](04_invoking_subprograms/#invoking_subprograms). The rules for accessing variables based upon block location is described in [Accessing Subprogram Variables](07_accessing_subprogram_variables/#accessing_subprogram_variables). +The rules for invoking subprograms based on block location are described starting with [Invoking subprograms](04_invoking_subprograms/#invoking_subprograms). The rules for accessing variables based on block location are described in [Accessing subprogram variables](07_accessing_subprogram_variables/#accessing_subprogram_variables). diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx index 6952b0bc17f..5bfca48c725 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx @@ -4,39 +4,39 @@ title: "Invoking subprograms" -A subprogram is invoked in the same manner as a standalone procedure or function by specifying its name and any actual parameters. +Invoke a subprogram in the same manner as a standalone procedure or function by specifying its name and any actual parameters. -The subprogram may be invoked with none, one, or more qualifiers, which are the names of the parent subprograms or labeled anonymous blocks forming the ancestor hierarchy from where the subprogram has been declared. +You can invoke the subprogram with none, one, or more qualifiers. Qualifiers are the names of the parent subprograms or labeled anonymous blocks forming the ancestor hierarchy from which the subprogram was declared. -The invocation is specified as a dot-separated list of qualifiers ending with the subprogram name and any of its arguments as shown by the following: +The invocation is specified as a dot-separated list of qualifiers ending with the subprogram name and any of its arguments: ```text [[.][...].] [()] ``` -If specified, `qualifier_n` is the subprogram in which `subprog` has been declared in its declaration section. The preceding list of qualifiers must reside in a continuous path up the hierarchy from `qualifier_n` to `qualifier_1. qualifier_1` may be any ancestor subprogram in the path as well as any of the following: +If specified, `qualifier_n` is the subprogram in which `subprog` was declared in its declaration section. The preceding list of qualifiers must reside in a continuous path up the hierarchy from `qualifier_n` to `qualifier_1`. `qualifier_1` can be any ancestor subprogram in the path as well as any of the following: - Standalone procedure name containing the subprogram -- Standalone function name containing subprogram +- Standalone function name containing the subprogram - Package name containing the subprogram -- Object type name containing the subprogram within an object type method -- An anonymous block label included prior to the `DECLARE` keyword if a declaration section exists, or prior to the `BEGIN` keyword if there is no declaration section. +- Object type name containing the subprogram in an object type method +- An anonymous block label included prior to the `DECLARE` keyword if a declaration section exists, or prior to the `BEGIN` keyword if there is no declaration section !!! Note - `qualifier_1` may not be a schema name, otherwise an error is thrown upon invocation of the subprogram. This EDB Postgres Advanced Server restriction is not compatible with Oracle databases, which allow use of the schema name as a qualifier. + `qualifier_1` can't be a schema name. If it is, an error is thrown when invoking the subprogram. This EDB Postgres Advanced Server restriction isn't compatible with Oracle databases, which allow the use of the schema name as a qualifier. -`arguments` is the list of actual parameters to be passed to the subprocedure or subfunction. +`arguments` is the list of actual parameters to pass to the subprocedure or subfunction. Upon invocation, the search for the subprogram occurs as follows: -- The invoked subprogram name of its type (that is, subprocedure or subfunction) along with any qualifiers in the specified order, (referred to as the invocation list) is used to find a matching set of blocks residing in the same hierarchical order. The search begins in the block hierarchy where the lowest level is the block from where the subprogram is invoked. The declaration of the subprogram must be in the SPL code prior to the code line where it is invoked when the code is observed from top to bottom. (An exception to this requirement can be accomplished using a forward declaration. See [Using Forward Declarations](05_using_forward_declarations/#using_forward_declarations) for information on forward declarations.) -- If the invocation list does not match the hierarchy of blocks starting from the block where the subprogram is invoked, a comparison is made by matching the invocation list starting with the parent of the previous starting block. In other words, the comparison progresses up the hierarchy. -- If there are sibling blocks of the ancestors, the invocation list comparison also includes the hierarchy of the sibling blocks, but always comparing in an upward level, never comparing the descendants of the sibling blocks. -- This comparison process continues up the hierarchies until the first complete match is found in which case the located subprogram is invoked. Note that the formal parameter list of the matched subprogram must comply with the actual parameter list specified for the invoked subprogram, otherwise an error occurs upon invocation of the subprogram. -- If no match is found after searching up to the standalone program, then an error is thrown upon invocation of the subprogram. +- The invoked subprogram name of its type (that is, subprocedure or subfunction) along with any qualifiers in the specified order (referred to as the invocation list) is used to find a matching set of blocks residing in the same hierarchical order. The search begins in the block hierarchy where the lowest level is the block from where the subprogram is invoked. The declaration of the subprogram must be in the SPL code prior to the code line where it's invoked when the code is observed from top to bottom. (You can achieve an exception to this requirement using a forward declaration. See [Using forward declarations](05_using_forward_declarations/#using_forward_declarations).) +- If the invocation list doesn't match the hierarchy of blocks starting from the block where the subprogram is invoked, a comparison is made by matching the invocation list starting with the parent of the previous starting block. In other words, the comparison progresses up the hierarchy. +- If there are sibling blocks of the ancestors, the invocation list comparison also includes the hierarchy of the sibling blocks but always comparing in an upward level. It does not compare the descendants of the sibling blocks. +- This comparison process continues up the hierarchies until the first complete match is found, in which case the located subprogram is invoked. The formal parameter list of the matched subprogram must comply with the actual parameter list specified for the invoked subprogram. Otherwise an error occurs when invoking the subprogram. +- If no match is found after searching up to the standalone program, then an error is thrown when invoking the subprogram. !!! Note - The EDB Postgres Advanced Server search algorithm for subprogram invocation is not quite compatible with Oracle databases. For Oracle, the search looks for the first match of the first qualifier (that is `qualifier_1`). When such a match is found, all remaining qualifiers, the subprogram name, subprogram type, and arguments of the invocation must match the hierarchy content where the matching first qualifier is found, otherwise an error is thrown. For EDB Postgres Advanced Server, a match is not found unless all qualifiers, the subprogram name, and the subprogram type of the invocation match the hierarchy content. If such an exact match is not initially found, EDB Postgres Advanced Server continues the search progressing up the hierarchy. + The EDB Postgres Advanced Server search algorithm for subprogram invocation isn't completely compatible with Oracle databases. For Oracle, the search looks for the first match of the first qualifier (that is, `qualifier_1`). When such a match is found, all remaining qualifiers, the subprogram name, subprogram type, and arguments of the invocation must match the hierarchy content where the matching first qualifier is found. Otherwise an error is thrown. For EDB Postgres Advanced Server, a match isn't found unless all qualifiers, the subprogram name, and the subprogram type of the invocation match the hierarchy content. If such an exact match isn't initially found, EDB Postgres Advanced Server continues the search progressing up the hierarchy. The location of subprograms relative to the block from where the invocation is made can be accessed as follows: @@ -44,18 +44,16 @@ The location of subprograms relative to the block from where the invocation is m - Subprograms declared in the parent or other ancestor blocks can be invoked from the child block of the parent or other ancestors. - Subprograms declared in sibling blocks can be called from a sibling block or from any descendent block of the sibling. -However, the following location of subprograms cannot be accessed relative to the block from where the invocation is made: +However, you can't access the following location of subprograms relative to the block from where the invocation is made: -- Subprograms declared in blocks that are descendants of the block from where the invocation is attempted. -- Subprograms declared in blocks that are descendants of a sibling block from where the invocation is attempted. - -The following examples illustrate the various conditions previously described. +- Subprograms declared in blocks that are descendants of the block from where the invocation is attempted +- Subprograms declared in blocks that are descendants of a sibling block from where the invocation is attempted ## Invoking locally declared subprograms -The following example contains a single hierarchy of blocks contained within standalone procedure `level_0`. Within the executable section of procedure `level_1a`, the means of invoking the local procedure `level_2a` are shown, both with and without qualifiers. +Thid example contains a single hierarchy of blocks contained in thr nstandalone procedure `level_0`. In the executable section of the procedure `level_1a`, the means of invoking the local procedure `level_2a` are shown, with and without qualifiers. -Also note that access to the descendant of local procedure `level_2a`, which is procedure `level_3a`, is not permitted, with or without qualifiers. These calls are commented out in the example. +Access to the descendant of the local procedure `level_2a`, which is the procedure `level_3a`, isn't permitted, with or without qualifiers. These calls are commented out in the example. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -90,7 +88,7 @@ BEGIN END level_0; ``` -When the standalone procedure is invoked, the output is the following, which indicates that procedure `level_2a` is successfully invoked from the calls in the executable section of procedure `level_1a`. +When the standalone procedure is invoked, the output is the following, which indicates that procedure `level_2a` is successfully invoked from the calls in the executable section of procedure `level_1a`: ```text BEGIN @@ -109,13 +107,13 @@ BLOCK level_0 END BLOCK level_0 ``` -If you were to attempt to run procedure `level_0` with any of the calls to the descendent block uncommented, then an error occurs. +If you try to run the procedure `level_0` with any of the calls to the descendent block uncommented, then an error occurs. ## Invoking subprograms declared in ancestor blocks -The following example shows how subprograms can be invoked that are declared in parent and other ancestor blocks relative to the block where the invocation is made. +This example shows how to invoke subprograms that are declared in parent and other ancestor blocks relative to the block where the invocation is made. -In this example, the executable section of procedure `level_3a` invokes procedure `level_2a`, which is its parent block. (Note that `v_cnt` is used to avoid an infinite loop.) +In this example, the executable section of procedure `level_3a` invokes procedure `level_2a`, which is its parent block. `v_cnt` is used to avoid an infinite loop. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -152,7 +150,7 @@ BEGIN END level_0; ``` -The following is the resulting output: +The following is the output: ```text BEGIN @@ -173,7 +171,7 @@ BLOCK level_0 END BLOCK level_0 ``` -In a similar example, the executable section of procedure `level_3a` invokes procedure `level_1a`, which is further up the ancestor hierarchy. (Note that `v_cnt` is used to avoid an infinite loop.) +In a similar example, the executable section of the procedure `level_3a` invokes the procedure `level_1a`, which is further up the ancestor hierarchy. `v_cnt` is used to avoid an infinite loop. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -210,7 +208,7 @@ BEGIN END level_0; ``` -The following is the resulting output: +The following is the output: ```text BEGIN @@ -235,11 +233,11 @@ END BLOCK level_0 ## Invoking subprograms declared in sibling blocks -The following examples show how subprograms can be invoked that are declared in a sibling block relative to the local, parent, or other ancestor blocks from where the invocation of the subprogram is made. +These examples show how you can invoke subprograms that are declared in a sibling block relative to the local, parent, or other ancestor blocks from where the invocation of the subprogram is made. -In this example, the executable section of procedure `level_1b` invokes procedure `level_1a`, which is its sibling block. Both are local to standalone procedure `level_0`. +In this example, the executable section of the procedure `level_1b` invokes the procedure `level_1a`, which is its sibling block. Both are local to the standalone procedure `level_0`. -Note that invocation of `level_2a` or equivalently, `level_1a.level_2a` from within procedure `level_1b` is commented out as this call would result in an error. Invoking a descendent subprogram `(level_2a)` of sibling block `(level_1a)` is not permitted. +Invoking `level_2a` or, equivalently, `level_1a.level_2a` from the procedure `level_1b` is commented out as this call results in an error. Invoking a descendent subprogram (`level_2a`) of sibling block (`level_1a`) isn't permitted. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -273,7 +271,7 @@ BEGIN END level_0; ``` -The following is the resulting output: +The following is the output: ```text BEGIN @@ -288,7 +286,7 @@ BLOCK level_0 END BLOCK level_0 ``` -In the following example, procedure `level_1a`, which is the sibling of procedure `level_1b`, which is an ancestor of procedure `level_3b` is successfully invoked. +In this example, the procedure `level_1a` is successfully invoked. It is the sibling of the procedure `level_1b`, which is an ancestor of the procedure `level_3b`. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -328,7 +326,7 @@ BEGIN END level_0; ``` -The following is the resulting output: +The following is the output: ```text BEGIN diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx index 66d5e5814c6..a28c2503d92 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx @@ -4,15 +4,15 @@ title: "Using forward declarations" -As discussed so far, when a subprogram is to be invoked, it must have been declared somewhere in the hierarchy of blocks within the standalone program, but prior to where it is invoked. In other words, when scanning the SPL code from beginning to end, the subprogram declaration must be found before its invocation. +When you want to invoke a subprogram, you must declare it in the hierarchy of blocks in the standalone program prior to where you invoke it. In other words, when scanning the SPL code from beginning to end, the subprogram declaration must appear before its invocation. -However, there is a method of constructing the SPL code so that the full declaration of the subprogram (that is, its optional declaration section, its mandatory executable section, and optional exception section) appears in the SPL code after the point in the code where it is invoked. +However, you can construct the SPL code so that the full declaration of the subprogram appears in the SPL code after the point in the code where it is invoked. The full declaration includes its optional declaration section, its mandatory executable section, and optional exception section) -This is accomplished by inserting a *forward declaration* in the SPL code prior to its invocation. The forward declaration is the specification of a subprocedure or subfunction name, formal parameters, and return type if it is a subfunction. +You can do this by inserting a *forward declaration* in the SPL code prior to its invocation. The forward declaration is the specification of a subprocedure or subfunction name, formal parameters, and return type if it is a subfunction. -The full subprogram specification consisting of the optional declaration section, the executable section, and the optional exception section must be specified in the same declaration section as the forward declaration, but may appear following other subprogram declarations that invoke this subprogram with the forward declaration. +You must specify the full subprogram consisting of the optional declaration section, the executable section, and the optional exception section in the same declaration section as the forward declaration. However it can appear following other subprogram declarations that invoke this subprogram with the forward declaration. -Typical usage of a forward declaration is when two subprograms invoke each other as shown by the following: +Typical use of a forward declaration is when two subprograms invoke each other: ```text DECLARE @@ -43,7 +43,7 @@ BEGIN END; ``` -Subfunction `test_max` invokes subfunction `add_one`, which also invokes subfunction `test_max`, so a forward declaration is required for one of the subprograms, which is implemented for `add_one` at the beginning of the anonymous block declaration section. +Subfunction `test_max` invokes subfunction `add_one`, which also invokes subfunction `test_max`. A forward declaration is required for one of the subprograms, which is implemented for `add_one` at the beginning of the anonymous block declaration section. The resulting output from the anonymous block is as follows: diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx index bd8bd10f401..a557ee141bd 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx @@ -4,40 +4,40 @@ title: "Overloading subprograms" -Generally, subprograms of the same type (subprocedure or subfunction) with the same name, and same formal parameter specification can appear multiple times within the same standalone program as long as they are not sibling blocks (that is, the subprograms are not declared in the same local block). +Generally, subprograms of the same type (subprocedure or subfunction) with the same name and same formal parameter specification can appear multiple times in the same standalone program as long as they aren't sibling blocks (that is, the subprograms aren't declared in the same local block). -Each subprogram can be individually invoked depending upon the use of qualifiers and the location where the subprogram invocation is made as discussed in the previous sections. +You can invoke aach subprogram individually depending on the use of qualifiers and the location where the subprogram invocation is made. -It is however possible to declare subprograms, even as siblings, that are of the same subprogram type and name as long as certain aspects of the formal parameters differ. These characteristics (subprogram type, name, and formal parameter specification) is generally known as a program’s *signature*. +However, it's possible to declare subprograms, even as siblings, that are of the same subprogram type and name as long as certain aspects of the formal parameters differ. These characteristics (subprogram type, name, and formal parameter specification) are generally known as a program’s *signature*. The declaration of multiple subprograms where the signatures are identical except for certain aspects of the formal parameter specification is referred to as subprogram *overloading*. -Thus, the determination of which particular overloaded subprogram is to be invoked is determined by a match of the actual parameters specified by the subprogram invocation and the formal parameter lists of the overloaded subprograms. +Thus, the particular overloaded subprogram to invoke is determined by a match of the actual parameters specified by the subprogram invocation and the formal parameter lists of the overloaded subprograms. Any of the following differences permit overloaded subprograms: - The number of formal parameters are different. -- At least one pair of data types of the corresponding formal parameters (that is, compared according to the same order of appearance in the formal parameter list) are different, but are not aliases. Data type aliases are discussed later in this section. +- At least one pair of data types of the corresponding formal parameters (that is, compared according to the same order of appearance in the formal parameter list) are different but aren't aliases. -Note that the following differences alone don't permit overloaded subprograms: +The following differences alone don't permit overloaded subprograms: - Different formal parameter names -- Different parameter modes `(IN, IN OUT, OUT)` for the corresponding formal parameters +- Different parameter modes (`IN`, `IN OUT`, `OUT) for the corresponding formal parameters - For subfunctions, different data types in the `RETURN` clause -As previously indicated, one of the differences allowing overloaded subprograms are different data types. +One of the differences allowing overloaded subprograms is different data types. However, certain data types have alternative names referred to as *aliases*, which can be used for the table definition. -For example, there are fixed length character data types that can be specified as `CHAR` or `CHARACTER`. There are variable length character data types that can be specified 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 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](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/). -Thus, when attempting to create overloaded subprograms, the formal parameter data types are not considered different if the specified data types are aliases of each other. +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. -It can be determined if certain data types are aliases of other types by displaying the table definition containing the data types in question. +You can determine if certain data types are aliases of other types by displaying the table definition containing the data types. -For example, the following table definition contains some data types and their aliases. +For example, the following table definition contains some data types and their aliases: ```text CREATE TABLE data_type_aliases ( @@ -88,16 +88,16 @@ Using the PSQL `\d` command to display the table definition, the Type column dis dt_varchar | character varying(4) | ``` -In the example, the base set of data types are `bytea, integer, real, double precision, numeric, character`, and `character varying`. +In the example, the base set of data types are `bytea`, `integer`, `real`, `double precision`, `numeric`, `character`, and `character varying`. -When attempting to declare overloaded subprograms, a pair of formal parameter data types that are aliases would not be sufficient to allow subprogram overloading. Thus, parameters with data types `INTEGER` and `PLS_INTEGER` cannot overload a pair of subprograms, but data types `INTEGER` and `REAL`, or `INTEGER` and `FLOAT`, or `INTEGER` and `NUMBER` can overload the subprograms. +When attempting to declare overloaded subprograms, a pair of formal parameter data types that are aliases aren't sufficient to allow subprogram overloading. Thus, parameters with data types `INTEGER` and `PLS_INTEGER` can't overload a pair of subprograms, but data types `INTEGER` and `REAL`, `INTEGER` and `FLOAT`, or `INTEGER` and `NUMBER` can overload the subprograms. !!! Note - The overloading rules based upon formal parameter data types are not compatible with Oracle databases. Generally, the EDB Postgres Advanced Server rules are more flexible, and certain combinations are allowed in EDB Postgres Advanced Server that would result in an error when attempting to create the procedure or function in Oracle databases. + The overloading rules based on formal parameter data types aren't compatible with Oracle databases. Generally, the EDB Postgres Advanced Server rules are more flexible, and certain combinations are allowed in EDB Postgres Advanced Server that result in an error when attempting to create the procedure or function in Oracle databases. -For certain pairs of data types used for overloading, casting of the arguments specified by the subprogram invocation may be required to avoid an error encountered during runtime of the subprogram. Invocation of a subprogram must include the actual parameter list that can specifically identify the data types. Certain pairs of overloaded data types may require the `CAST` function to explicitly identify data types. For example, pairs of overloaded data types that may require casting during the invocation are `CHAR` and `VARCHAR2`, or `NUMBER` and `REAL`. +For certain pairs of data types used for overloading, you might need to cast the arguments specified by the subprogram invocationto avoid an error encountered during runtime of the subprogram. Invoking a subprogram must include the actual parameter list that can specifically identify the data types. Certain pairs of overloaded data types might require the `CAST` function to explicitly identify data types. For example, pairs of overloaded data types that might require casting during the invocation are `CHAR` and `VARCHAR2`, or `NUMBER` and `REAL`. -The following example shows a group of overloaded subfunctions invoked from within an anonymous block. The executable section of the anonymous block contains the use of the `CAST` function to invoke overloaded functions with certain data types. +This example shows a group of overloaded subfunctions invoked from an anonymous block. The executable section of the anonymous block contains the use of the `CAST` function to invoke overloaded functions with certain data types. ```text DECLARE diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx index a2e01ebc93e..977bd13d5fe 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx @@ -4,49 +4,49 @@ title: "Accessing subprogram variables" -Variable declared in blocks such as subprograms or anonymous blocks can be accessed from the executable section or the exception section of other blocks depending upon their relative location. +You can access variables declared in blocks, such as subprograms or anonymous blocks, from the executable section or the exception section of other blocks depending on their relative location. -Accessing a variable means being able to reference it within a SQL statement or an SPL statement as is done with any local variable. +Accessing a variable means being able to reference it in a SQL statement or an SPL statement as you can with any local variable. !!! Note - If the subprogram signature contains formal parameters, these may be accessed in the same manner as local variables of the subprogram. In this section, all discussion related to variables of a subprogram also applies to formal parameters of the subprogram. + If the subprogram signature contains formal parameters, you can access these in the same way as local variables of the subprogram. All discussion related to variables of a subprogram also applies to formal parameters of the subprogram. -Access of variables not only includes those defined as a data type, but also includes others such as record types, collection types, and cursors. +Accessing variables includes not only those defined as a data type but also includes others such as record types, collection types, and cursors. -The variable may be accessed by at most one qualifier, which is the name of the subprogram or labeled anonymous block in which the variable has been locally declared. +At most one qualifier can access the variable. The qualifier is the name of the subprogram or labeled anonymous block in which the variable was locally declared. -The syntax to reference a variable is shown by the following: +The syntax to reference a variable is: ```text [.] ``` -If specified, `qualifier` is the subprogram or labeled anonymous block in which `variable` has been declared in its declaration section (that is, it is a local variable). +If specified, `qualifier` is the subprogram or labeled anonymous block in which `variable` was declared in its declaration section (that is, it is a local variable). !!! Note - In EDB Postgres Advanced Server, there is only one circumstance where two qualifiers are permitted. This scenario is for accessing public variables of packages where the reference can be specified in the following format: + In EDB Postgres Advanced Server, there is only one circumstance in which two qualifiers are permitted. This scenario is for accessing public variables of packages where you can specify the reference in the following format: ```text schema_name.package_name.public_variable_name ``` -For more information about supported package syntax, see the *Database Compatibility for Oracle Developers Built-In Package Guide*. +For more information about supported package syntax, see [Database Compatibility for Oracle Developers: Built-in Package](/epas_compat_bip_guide/03_built-in_packages/). -The following summarizes how variables can be accessed: +You can access variables in the following ways: -- Variables can be accessed as long as the block in which the variable has been locally declared is within the ancestor hierarchical path starting from the block containing the reference to the variable. Such variables declared in ancestor blocks are referred to as *global variables*. -- If a reference to an unqualified variable is made, the first attempt is to locate a local variable of that name. If such a local variable does not exist, then the search for the variable is made in the parent of the current block, and so forth, proceeding up the ancestor hierarchy. If such a variable is not found, then an error occurs upon invocation of the subprogram. -- If a reference to a qualified variable is made, the same search process is performed as described in the previous bullet point, but searching for the first match of the subprogram or labeled anonymous block that contains the local variable. The search proceeds up the ancestor hierarchy until a match is found. If such a match is not found, then an error occurs upon invocation of the subprogram. +- Variables can be accessed as long as the block in which the variable was locally declared is in the ancestor hierarchical path starting from the block containing the reference to the variable. Such variables declared in ancestor blocks are referred to as *global variables*. +- If a reference to an unqualified variable is made, the first attempt is to locate a local variable of that name. If such a local variable doesn't exist, then the search for the variable is made in the parent of the current block, and so forth, proceeding up the ancestor hierarchy. If such a variable isn't found, then an error occurs when the subprogram is invoked. +- If a reference to a qualified variable is made, the same search process is performed but searching for the first match of the subprogram or labeled anonymous block that contains the local variable. The search proceeds up the ancestor hierarchy until a match is found. If such a match isn't found, then an error occurs when the subprogram is invoked. -The following location of variables cannot be accessed relative to the block from where the reference to the variable is made: +You can't access the following location of variables relative to the block from where the reference to the variable is made: -- Variables declared in a descendent block cannot be accessed, -- Variables declared in a sibling block, a sibling block of an ancestor block, or any descendants within the sibling block cannot be accessed. +- Variables declared in a descendent block +- Variables declared in a sibling block, a sibling block of an ancestor block, or any descendants within the sibling block !!! Note - The EDB Postgres Advanced Server process for accessing variables is not compatible with Oracle databases. For Oracle, any number of qualifiers can be specified and the search is based upon the first match of the first qualifier in a similar manner to the Oracle matching algorithm for invoking subprograms. + The EDB Postgres Advanced Server process for accessing variables isn't compatible with Oracle databases. For Oracle, you can specify any number of qualifiers, and the search is based on the first match of the first qualifier in a similar manner to the Oracle matching algorithm for invoking subprograms. -The following example displays how variables in various blocks are accessed, with and without qualifiers. The lines that are commented out illustrate attempts to access variables that would result in an error. +This example shows how variables in various blocks are accessed, with and without qualifiers. The lines that are commented out show attempts to access variables that result in an error. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -123,7 +123,7 @@ BLOCK level_0 END BLOCK level_0 ``` -The following example shows similar access attempts when all variables in all blocks have the same name: +This example shows similar access attempts when all variables in all blocks have the same name: ```text CREATE OR REPLACE PROCEDURE level_0 @@ -194,7 +194,7 @@ BLOCK level_0 END BLOCK level_0 ``` -As previously discussed, the labels on anonymous blocks can also be used to qualify access to variables. The following example shows variable access within a set of nested anonymous blocks: +You can also use the labels on anonymous blocks to qualify access to variables. This example shows variable access in a set of nested anonymous blocks: ```text DECLARE @@ -251,7 +251,7 @@ BLOCK level_0 END BLOCK level_0 ``` -The following example is an object type whose object type method, `display_emp`, contains record type `emp_typ` and subprocedure `emp_sal_query`. Record variable `r_emp` declared locally to `emp_sal_query` is able to access the record type `emp_typ` declared in the parent block `display_emp`. +This example is an object type whose object type method, `display_emp`, contains record type `emp_typ` and the subprocedure `emp_sal_query`. Record variable `r_emp` declared locally to `emp_sal_query` can access the record type `emp_typ` declared in the parent block `display_emp`. ```text CREATE OR REPLACE TYPE emp_pay_obj_typ AS OBJECT @@ -303,7 +303,7 @@ CREATE OR REPLACE TYPE BODY emp_pay_obj_typ AS END; ``` -The following is the output displayed when an instance of the object type is created and procedure `display_emp` is invoked: +The following is the output displayed when an instance of the object type is created and the procedure `display_emp` is invoked: ```text DECLARE @@ -322,7 +322,7 @@ Dept # : 30 Employee's salary does not exceed the department average of 1566.67 ``` -The following example is a package with three levels of subprocedures. A record type, collection type, and cursor type declared in the upper level procedure can be accessed by the descendent subprocedure. +This example is a package with three levels of subprocedures. A record type, collection type, and cursor type declared in the upper-level procedure can be accessed by the descendent subprocedure. ```text CREATE OR REPLACE PACKAGE emp_dept_pkg @@ -377,7 +377,7 @@ IS END; ``` -The following is the output displayed when the top level package procedure is invoked: +The following is the output displayed when the top-level package procedure is invoked: ```text BEGIN diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx index bb7c9955002..862d2785017 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx @@ -4,26 +4,25 @@ title: "Subprograms: subprocedures and subfunctions" -The capability and functionality of SPL procedure and function programs can be used in an advantageous manner to build well-structured and maintainable programs by organizing the SPL code into subprocedures and subfunctions. +You can use the capability and functionality of SPL procedure and function programs can be used in an advantageous manner to build well-structured and maintainable programs by organizing the SPL code into subprocedures and subfunctions. -The same SPL code can be invoked multiple times from different locations within a relatively large SPL program by declaring subprocedures and subfunctions within the SPL program. +You can invoke the same SPL code can be invoked multiple times from different locations in a relatively large SPL program by declaring subprocedures and subfunctions in the SPL program. Subprocedures and subfunctions have the following characteristics: - The syntax, structure, and functionality of subprocedures and subfunctions are practically identical to standalone procedures and functions. The major difference is the use of the keyword `PROCEDURE` or `FUNCTION` instead of `CREATE PROCEDURE` or `CREATE FUNCTION` to declare the subprogram. -- Subprocedures and subfunctions provide isolation for the identifiers (that is, variables, cursors, types, and other subprograms) declared within itself. That is, these identifiers cannot be accessed nor altered from the upper, parent level SPL programs or subprograms outside of the subprocedure or subfunction. This ensures that the subprocedure and subfunction results are reliable and predictable. -- The declaration section of subprocedures and subfunctions can include its own subprocedures and subfunctions. Thus, a multi-level hierarchy of subprograms can exist in the standalone program. Within the hierarchy, a subprogram can access the identifiers of upper level parent subprograms and also invoke upper level parent subprograms. However, the same access to identifiers and invocation cannot be done for lower level child subprograms in the hierarchy. +- Subprocedures and subfunctions provide isolation for the identifiers (that is, variables, cursors, types, and other subprograms) declared within itself. That is, these identifiers can't be accessed or altered from the upper, parent level SPL programs or subprograms outside of the subprocedure or subfunction. This ensures that the subprocedure and subfunction results are reliable and predictable. +- The declaration section of subprocedures and subfunctions can include its own subprocedures and subfunctions. Thus, a multi-level hierarchy of subprograms can exist in the standalone program. In the hierarchy, a subprogram can access the identifiers of upper-level parent subprograms and also invoke upperplevel parent subprograms. However, the same access to identifiers and invocation can't be done for lower-level child subprograms in the hierarchy. -Subprocedures and subfunctions can be declared and invoked from within any of the following types of SPL programs: +You can declare and invoke subprocedures and subfunctions from any of the following types of SPL programs: - Standalone procedures and functions - Anonymous blocks - Triggers - Packages - Procedure and function methods of an object type body -- Subprocedures and subfunctions declared within any of the preceding programs +- Subprocedures and subfunctions declared in any of the preceding programs -The rules regarding subprocedure and subfunction structure and access are discussed in more detail in the next sections.
From 545b1567312dafce59f013f5098febbd6083234b Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 15 Nov 2022 15:53:35 -0500 Subject: [PATCH 06/32] Second edit of section --- .../01_creating_a_subprocedure.mdx | 2 +- .../02_creating_a_subfunction.mdx | 2 +- .../03_block_relationships.mdx | 10 +++---- .../04_invoking_subprograms.mdx | 30 +++++++++---------- .../05_using_forward_declarations.mdx | 4 +-- .../06_overloading_subprograms.mdx | 8 ++--- .../07_accessing_subprogram_variables.mdx | 6 ++-- .../index.mdx | 10 +++---- 8 files changed, 36 insertions(+), 36 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx index 45fb44b76dd..67fd019149e 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx @@ -8,7 +8,7 @@ The `PROCEDURE` clause specified in the declaration section defines and names a The term *block* refers to the SPL block structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks are the structures for standalone procedures and functions, anonymous blocks, subprograms, triggers, packages, and object type methods. -The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block and is therefore the SPL code can access it in the executable section and optional exception section of that block. +The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block. Therefore, the SPL code can access it in the executable section and optional exception section of that block. You can declare subprocedures only after all the other variable, cursor, and type declarations included in the declaration section. Subprograms must be the last set of declarations. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx index 976d92bfd6a..bf0a6f86351 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx @@ -37,7 +37,7 @@ Where: ## Examples -The following example shows the use of a recursive subfunction: +This example shows the use of a recursive subfunction: ```text DECLARE diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx index 07320f03c07..f655e25b377 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx @@ -4,24 +4,24 @@ title: "Block relationships" -You can declare the relationship between blocks in an SPL program. The ability to invoke subprograms and access identifiers declared in a block depends upon this relationship. +You can declare the relationship between blocks in an SPL program. The ability to invoke subprograms and access identifiers declared in a block depends on this relationship. The following are the basic terms: - A *block* is the basic SPL structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks implement standalone procedure and function programs, anonymous blocks, triggers, packages, and subprocedures and subfunctions. -- An identifier (variable, cursor, type, or subprogram) *local to a block* means that it's declared in the declaration section of the given block. Such local identifiers are accessible from the executable section and optional exception section of the block. +- An identifier (variable, cursor, type, or subprogram) *local to a block* means that it's declared in the declaration section of the given block. You can access such local identifiers from the executable section and optional exception section of the block. - The *parent block* contains the declaration of another block, that is, the *child block*. - *Descendent blocks* are the set of blocks forming the child relationship starting from a given parent block. - *Ancestor blocks* are the set of blocks forming the parental relationship starting from a given child block. - The set of descendent (ancestor) blocks form a *hierarchy*. -- The *level* is an ordinal number of a given block from the highest, ancestor block. For example, given a standalone procedure, the subprograms declared in the declaration section of this procedure are all at the same level, for example, level 1. Additional subprograms in the declaration section of the subprograms declared in the standalone procedure are at the next level, that is, level 2. -- The *sibling blocks* are the set of blocks that have the same parent block,that is, they are all locally declared in the same block. Sibling blocks are always at the same level relative to each other. +- The *level* is an ordinal number of a given block from the highest ancestor block. For example, given a standalone procedure, the subprograms declared in the declaration section of this procedure are all at the same level, such as level 1. Additional subprograms in the declaration section of the subprograms declared in the standalone procedure are at the next level, that is, level 2. +- The *sibling blocks* are the set of blocks that have the same parent block, that is, they are all locally declared in the same block. Sibling blocks are at the same level relative to each other. The following schematic of a set of procedure declaration sections provides an example of a set of blocks and their relationships to their surrounding blocks. The two vertical lines on the left-hand side of the blocks indicate there are two pairs of sibling blocks. `block_1a` and `block_1b` is one pair, and `block_2a` and `block_2b` is the second pair. -The relationship of each block with its ancestors is shown on the right-hand side of the blocks. Three hierarchical paths are formed when progressing up the hierarchy from the lowest level child blocks. The first consists of `block_0`, `block_1a`, `block_2a`, and `block_3`. The second is `block_0`, `block_1a`, and `block_2b`. The third is `block_0`, `block_1b`, and `block_2b`. +The relationship of each block with its ancestors is shown on the right-hand side of the blocks. Three hierarchical paths are formed when progressing up the hierarchy from the lowest-level child blocks. The first consists of `block_0`, `block_1a`, `block_2a`, and `block_3`. The second is `block_0`, `block_1a`, and `block_2b`. The third is `block_0`, `block_1b`, and `block_2b`. ```text CREATE PROCEDURE block_0 diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx index 5bfca48c725..ec00f66d497 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx @@ -6,9 +6,9 @@ title: "Invoking subprograms" Invoke a subprogram in the same manner as a standalone procedure or function by specifying its name and any actual parameters. -You can invoke the subprogram with none, one, or more qualifiers. Qualifiers are the names of the parent subprograms or labeled anonymous blocks forming the ancestor hierarchy from which the subprogram was declared. +You can invoke the subprogram with zero, one, or more qualifiers. Qualifiers are the names of the parent subprograms or labeled anonymous blocks forming the ancestor hierarchy from which the subprogram was declared. -The invocation is specified as a dot-separated list of qualifiers ending with the subprogram name and any of its arguments: +Invoke the subprogram using a dot-separated list of qualifiers ending with the subprogram name and any of its arguments: ```text [[.][...].] [()] @@ -27,31 +27,31 @@ If specified, `qualifier_n` is the subprogram in which `subprog` was declared in `arguments` is the list of actual parameters to pass to the subprocedure or subfunction. -Upon invocation, the search for the subprogram occurs as follows: +When you invoke the subprogram, the search for the subprogram occurs as follows: - The invoked subprogram name of its type (that is, subprocedure or subfunction) along with any qualifiers in the specified order (referred to as the invocation list) is used to find a matching set of blocks residing in the same hierarchical order. The search begins in the block hierarchy where the lowest level is the block from where the subprogram is invoked. The declaration of the subprogram must be in the SPL code prior to the code line where it's invoked when the code is observed from top to bottom. (You can achieve an exception to this requirement using a forward declaration. See [Using forward declarations](05_using_forward_declarations/#using_forward_declarations).) - If the invocation list doesn't match the hierarchy of blocks starting from the block where the subprogram is invoked, a comparison is made by matching the invocation list starting with the parent of the previous starting block. In other words, the comparison progresses up the hierarchy. -- If there are sibling blocks of the ancestors, the invocation list comparison also includes the hierarchy of the sibling blocks but always comparing in an upward level. It does not compare the descendants of the sibling blocks. +- If there are sibling blocks of the ancestors, the invocation list comparison also includes the hierarchy of the sibling blocks but always comparing in an upward level. It doesn't compare the descendants of the sibling blocks. - This comparison process continues up the hierarchies until the first complete match is found, in which case the located subprogram is invoked. The formal parameter list of the matched subprogram must comply with the actual parameter list specified for the invoked subprogram. Otherwise an error occurs when invoking the subprogram. - If no match is found after searching up to the standalone program, then an error is thrown when invoking the subprogram. !!! Note The EDB Postgres Advanced Server search algorithm for subprogram invocation isn't completely compatible with Oracle databases. For Oracle, the search looks for the first match of the first qualifier (that is, `qualifier_1`). When such a match is found, all remaining qualifiers, the subprogram name, subprogram type, and arguments of the invocation must match the hierarchy content where the matching first qualifier is found. Otherwise an error is thrown. For EDB Postgres Advanced Server, a match isn't found unless all qualifiers, the subprogram name, and the subprogram type of the invocation match the hierarchy content. If such an exact match isn't initially found, EDB Postgres Advanced Server continues the search progressing up the hierarchy. -The location of subprograms relative to the block from where the invocation is made can be accessed as follows: +You can access the location of subprograms relative to the block from where the invocation is made as follows: -- Subprograms declared in the local block can be invoked from the executable section or the exception section of the same block. -- Subprograms declared in the parent or other ancestor blocks can be invoked from the child block of the parent or other ancestors. -- Subprograms declared in sibling blocks can be called from a sibling block or from any descendent block of the sibling. +- You can invoke subprograms declared in the local block from the executable section or the exception section of the same block. +- You can invoke subprograms declared in the parent or other ancestor blocks from the child block of the parent or other ancestors. +- You can call subprograms declared in sibling blocks from a sibling block or from any descendent block of the sibling. -However, you can't access the following location of subprograms relative to the block from where the invocation is made: +However, you can't access the following locations of subprograms relative to the block from where the invocation is made: - Subprograms declared in blocks that are descendants of the block from where the invocation is attempted - Subprograms declared in blocks that are descendants of a sibling block from where the invocation is attempted ## Invoking locally declared subprograms -Thid example contains a single hierarchy of blocks contained in thr nstandalone procedure `level_0`. In the executable section of the procedure `level_1a`, the means of invoking the local procedure `level_2a` are shown, with and without qualifiers. +This example contains a single hierarchy of blocks contained in the standalone procedure `level_0`. In the executable section of the procedure `level_1a`, the means of invoking the local procedure `level_2a` are shown, with and without qualifiers. Access to the descendant of the local procedure `level_2a`, which is the procedure `level_3a`, isn't permitted, with or without qualifiers. These calls are commented out in the example. @@ -88,7 +88,7 @@ BEGIN END level_0; ``` -When the standalone procedure is invoked, the output is the following, which indicates that procedure `level_2a` is successfully invoked from the calls in the executable section of procedure `level_1a`: +When the standalone procedure is invoked, the output is the following. This output indicates that the procedure `level_2a` is successfully invoked from the calls in the executable section of the procedure `level_1a`: ```text BEGIN @@ -113,7 +113,7 @@ If you try to run the procedure `level_0` with any of the calls to the descenden This example shows how to invoke subprograms that are declared in parent and other ancestor blocks relative to the block where the invocation is made. -In this example, the executable section of procedure `level_3a` invokes procedure `level_2a`, which is its parent block. `v_cnt` is used to avoid an infinite loop. +In this example, the executable section of procedure `level_3a` invokes the procedure `level_2a`, which is its parent block. `v_cnt` is used to avoid an infinite loop. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -171,7 +171,7 @@ BLOCK level_0 END BLOCK level_0 ``` -In a similar example, the executable section of the procedure `level_3a` invokes the procedure `level_1a`, which is further up the ancestor hierarchy. `v_cnt` is used to avoid an infinite loop. +In a similar example, the executable section of the procedure `level_3a` invokes the procedure `level_1a`, which is further up the ancestor hierarchy. `v_cnt` is again used to avoid an infinite loop. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -237,7 +237,7 @@ These examples show how you can invoke subprograms that are declared in a siblin In this example, the executable section of the procedure `level_1b` invokes the procedure `level_1a`, which is its sibling block. Both are local to the standalone procedure `level_0`. -Invoking `level_2a` or, equivalently, `level_1a.level_2a` from the procedure `level_1b` is commented out as this call results in an error. Invoking a descendent subprogram (`level_2a`) of sibling block (`level_1a`) isn't permitted. +Invoking `level_2a` or, equivalently, `level_1a.level_2a` from the procedure `level_1b` is commented out as this call results in an error. Invoking a descendent subprogram (`level_2a`) of a sibling block (`level_1a`) isn't permitted. ```text CREATE OR REPLACE PROCEDURE level_0 @@ -286,7 +286,7 @@ BLOCK level_0 END BLOCK level_0 ``` -In this example, the procedure `level_1a` is successfully invoked. It is the sibling of the procedure `level_1b`, which is an ancestor of the procedure `level_3b`. +In this example, the procedure `level_1a` is successfully invoked. It's the sibling of the procedure `level_1b`, which is an ancestor of the procedure `level_3b`. ```text CREATE OR REPLACE PROCEDURE level_0 diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx index a28c2503d92..bd8d97796e7 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx @@ -6,9 +6,9 @@ title: "Using forward declarations" When you want to invoke a subprogram, you must declare it in the hierarchy of blocks in the standalone program prior to where you invoke it. In other words, when scanning the SPL code from beginning to end, the subprogram declaration must appear before its invocation. -However, you can construct the SPL code so that the full declaration of the subprogram appears in the SPL code after the point in the code where it is invoked. The full declaration includes its optional declaration section, its mandatory executable section, and optional exception section) +However, you can construct the SPL code so that the full declaration of the subprogram appears in the SPL code after the point in the code where it's invoked. (The full declaration includes its optional declaration section, its mandatory executable section, and optional exception section.) -You can do this by inserting a *forward declaration* in the SPL code prior to its invocation. The forward declaration is the specification of a subprocedure or subfunction name, formal parameters, and return type if it is a subfunction. +You can do this by inserting a *forward declaration* in the SPL code prior to its invocation. The forward declaration is the specification of a subprocedure or subfunction name, formal parameters, and return type if it's a subfunction. You must specify the full subprogram consisting of the optional declaration section, the executable section, and the optional exception section in the same declaration section as the forward declaration. However it can appear following other subprogram declarations that invoke this subprogram with the forward declaration. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx index a557ee141bd..adaba5e4452 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx @@ -22,7 +22,7 @@ Any of the following differences permit overloaded subprograms: The following differences alone don't permit overloaded subprograms: - Different formal parameter names -- Different parameter modes (`IN`, `IN OUT`, `OUT) for the corresponding formal parameters +- Different parameter modes (`IN`, `IN OUT`, `OUT`) for the corresponding formal parameters - For subfunctions, different data types in the `RETURN` clause One of the differences allowing overloaded subprograms is different data types. @@ -62,7 +62,7 @@ CREATE TABLE data_type_aliases ( ); ``` -Using the PSQL `\d` command to display the table definition, the Type column displays the data type internally assigned to each column based upon its data type in the table definition: +Using the PSQL `\d` command to display the table definition, the Type column displays the data type internally assigned to each column based on its data type in the table definition. ```text \d data_type_aliases @@ -90,12 +90,12 @@ Using the PSQL `\d` command to display the table definition, the Type column dis In the example, the base set of data types are `bytea`, `integer`, `real`, `double precision`, `numeric`, `character`, and `character varying`. -When attempting to declare overloaded subprograms, a pair of formal parameter data types that are aliases aren't sufficient to allow subprogram overloading. Thus, parameters with data types `INTEGER` and `PLS_INTEGER` can't overload a pair of subprograms, but data types `INTEGER` and `REAL`, `INTEGER` and `FLOAT`, or `INTEGER` and `NUMBER` can overload the subprograms. +When attempting to declare overloaded subprograms, a pair of formal parameter data types that are aliases aren't enough to allow subprogram overloading. Thus, parameters with data types `INTEGER` and `PLS_INTEGER` can't overload a pair of subprograms. However, data types `INTEGER` and `REAL`, `INTEGER` and `FLOAT`, or `INTEGER` and `NUMBER` can overload the subprograms. !!! Note The overloading rules based on formal parameter data types aren't compatible with Oracle databases. Generally, the EDB Postgres Advanced Server rules are more flexible, and certain combinations are allowed in EDB Postgres Advanced Server that result in an error when attempting to create the procedure or function in Oracle databases. -For certain pairs of data types used for overloading, you might need to cast the arguments specified by the subprogram invocationto avoid an error encountered during runtime of the subprogram. Invoking a subprogram must include the actual parameter list that can specifically identify the data types. Certain pairs of overloaded data types might require the `CAST` function to explicitly identify data types. For example, pairs of overloaded data types that might require casting during the invocation are `CHAR` and `VARCHAR2`, or `NUMBER` and `REAL`. +For certain pairs of data types used for overloading, you might need to cast the arguments specified by the subprogram invocation to avoid an error encountered during runtime of the subprogram. Invoking a subprogram must include the actual parameter list that can specifically identify the data types. Certain pairs of overloaded data types might require the `CAST` function to explicitly identify data types. For example, pairs of overloaded data types that might require casting during the invocation are `CHAR` and `VARCHAR2`, or `NUMBER` and `REAL`. This example shows a group of overloaded subfunctions invoked from an anonymous block. The executable section of the anonymous block contains the use of the `CAST` function to invoke overloaded functions with certain data types. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx index 977bd13d5fe..3c59b62d730 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx @@ -21,10 +21,10 @@ The syntax to reference a variable is: [.] ``` -If specified, `qualifier` is the subprogram or labeled anonymous block in which `variable` was declared in its declaration section (that is, it is a local variable). +If specified, `qualifier` is the subprogram or labeled anonymous block in which `variable` was declared in its declaration section (that is, it's a local variable). !!! Note - In EDB Postgres Advanced Server, there is only one circumstance in which two qualifiers are permitted. This scenario is for accessing public variables of packages where you can specify the reference in the following format: + In EDB Postgres Advanced Server, in only one circumstance are two qualifiers are permitted. This scenario is for accessing public variables of packages where you can specify the reference in the following format: ```text schema_name.package_name.public_variable_name @@ -251,7 +251,7 @@ BLOCK level_0 END BLOCK level_0 ``` -This example is an object type whose object type method, `display_emp`, contains record type `emp_typ` and the subprocedure `emp_sal_query`. Record variable `r_emp` declared locally to `emp_sal_query` can access the record type `emp_typ` declared in the parent block `display_emp`. +This example is an object type whose object type method, `display_emp`, contains the record type `emp_typ` and the subprocedure `emp_sal_query`. The record variable `r_emp` declared locally to `emp_sal_query` can access the record type `emp_typ` declared in the parent block `display_emp`. ```text CREATE OR REPLACE TYPE emp_pay_obj_typ AS OBJECT diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx index 862d2785017..a7970927fea 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx @@ -4,15 +4,15 @@ title: "Subprograms: subprocedures and subfunctions" -You can use the capability and functionality of SPL procedure and function programs can be used in an advantageous manner to build well-structured and maintainable programs by organizing the SPL code into subprocedures and subfunctions. +You can use the capability and functionality of SPL procedure and function programs to your advantage to build well-structured and maintainable programs by organizing the SPL code into subprocedures and subfunctions. -You can invoke the same SPL code can be invoked multiple times from different locations in a relatively large SPL program by declaring subprocedures and subfunctions in the SPL program. +You can invoke the same SPL code multiple times from different locations in a relatively large SPL program by declaring subprocedures and subfunctions in the SPL program. Subprocedures and subfunctions have the following characteristics: -- The syntax, structure, and functionality of subprocedures and subfunctions are practically identical to standalone procedures and functions. The major difference is the use of the keyword `PROCEDURE` or `FUNCTION` instead of `CREATE PROCEDURE` or `CREATE FUNCTION` to declare the subprogram. -- Subprocedures and subfunctions provide isolation for the identifiers (that is, variables, cursors, types, and other subprograms) declared within itself. That is, these identifiers can't be accessed or altered from the upper, parent level SPL programs or subprograms outside of the subprocedure or subfunction. This ensures that the subprocedure and subfunction results are reliable and predictable. -- The declaration section of subprocedures and subfunctions can include its own subprocedures and subfunctions. Thus, a multi-level hierarchy of subprograms can exist in the standalone program. In the hierarchy, a subprogram can access the identifiers of upper-level parent subprograms and also invoke upperplevel parent subprograms. However, the same access to identifiers and invocation can't be done for lower-level child subprograms in the hierarchy. +- The syntax, structure, and functionality of subprocedures and subfunctions are almost identical to standalone procedures and functions. The major difference is the use of the keyword `PROCEDURE` or `FUNCTION` instead of `CREATE PROCEDURE` or `CREATE FUNCTION` to declare the subprogram. +- Subprocedures and subfunctions provide isolation for the identifiers (that is, variables, cursors, types, and other subprograms) declared within itself. That is, you can't access or alter these identifiers from the upper, parent-level SPL programs or subprograms outside of the subprocedure or subfunction. This ensures that the subprocedure and subfunction results are reliable and predictable. +- The declaration section of subprocedures and subfunctions can include its own subprocedures and subfunctions. Thus, a multi-level hierarchy of subprograms can exist in the standalone program. In the hierarchy, a subprogram can access the identifiers of upper-level parent subprograms and also invoke upper-level parent subprograms. However, the same access to identifiers and invocation can't be done for lower-level child subprograms in the hierarchy. You can declare and invoke subprocedures and subfunctions from any of the following types of SPL programs: From 2afff599b98b3f507d0a20308c3ce8d29a4ac221 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 15 Nov 2022 17:01:20 -0500 Subject: [PATCH 07/32] edit or program security section --- .../01_execute_privilege.mdx | 28 ++++++------- .../02_database_object_name_resolution.mdx | 10 ++--- .../03_database_object_privileges.mdx | 2 +- .../04_definers_vs_invokers_rights.mdx | 16 +++---- .../05_security_example.mdx | 42 +++++++++---------- .../09_program_security/index.mdx | 10 ++--- 6 files changed, 53 insertions(+), 55 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx index 01117767a1d..d7480a92c0b 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx @@ -6,34 +6,34 @@ title: "EXECUTE privilege" An SPL program (function, procedure, or package) can begin execution only if any of the following are true: -- The current user is a superuser, or -- The current user has been granted `EXECUTE` privilege on the SPL program, or -- The current user inherits `EXECUTE` privilege on the SPL program by virtue of being a member of a group which does have such privilege, or -- `EXECUTE` privilege has been granted to the `PUBLIC` group. +- The current user is a superuser. +- The current user was granted `EXECUTE` privilege on the SPL program. +- The current user inherits `EXECUTE` privilege on the SPL program by virtue of being a member of a group that has this privilege. +- `EXECUTE` privilege was granted to the `PUBLIC` group. -Whenever an SPL program is created in EDB Postgres Advanced Server, `EXECUTE` privilege is automatically granted to the `PUBLIC` group by default, therefore, any user can immediately execute the program. +Whenever an SPL program is created in EDB Postgres Advanced Server, `EXECUTE` privilege is granted to the `PUBLIC` group by default. Therefore, any user can immediately execute the program. -This default privilege can be removed by using the `REVOKE EXECUTE` command. The following is an example: +You can remove this default privilege by using the `REVOKE EXECUTE` command. For example: ```text REVOKE EXECUTE ON PROCEDURE list_emp FROM PUBLIC; ``` -Explicit `EXECUTE` privilege on the program can then be granted to individual users or groups. +You can then grant explicit `EXECUTE` privilege on the program to individual users or groups. ```text GRANT EXECUTE ON PROCEDURE list_emp TO john; ``` -Now, user, `john`, can execute the `list_emp` program; other users who don't meet any of the conditions listed at the beginning of this section cannot. +Now, user `john` can execute the `list_emp` program. Other users who don't meet any of the required conditions can't. -Once a program begins execution, the next aspect of security is what privilege checks occur if the program attempts to perform an action on any database object including: +Once a program begins to execute, the next aspect of security is the privilege checks that occur if the program attempts to perform an action on any database object including: -- Reading or modifying table or view data. -- Creating, modifying, or deleting a database object such as a table, view, index, or sequence. -- Obtaining the current or next value from a sequence. -- Calling another program (function, procedure, or package). +- Reading or modifying table or view data +- Creating, modifying, or deleting a database object such as a table, view, index, or sequence +- Obtaining the current or next value from a sequence +- Calling another program (function, procedure, or package) Each such action can be protected by privileges on the database object either allowed or disallowed for the user. -Note that it is possible for a database to have more than one object of the same type with the same name, but each such object belonging to a different schema in the database. If this is the case, which object is being referenced by an SPL program? This is the topic of the next section. +It's possible for a database to have more than one object of the same type with the same name, but each such object belongs to a different schema in the database. If this is the case, which object is being referenced by an SPL program? For more information, see [Database object name resolution](02_database_object_name_resolution). \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx index dc28f90c83f..93a37aef223 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx @@ -4,9 +4,9 @@ title: "Database object name resolution" -A database object inside an SPL program may either be referenced by its qualified name or by an unqualified name. A qualified name is in the form of `schema.name` where `schema` is the name of the schema under which the database object with identifier, `name`, exists. An unqualified name does not have the `schema.` portion. When a reference is made to a qualified name, there is absolutely no ambiguity as to exactly which database object is intended – it either does or does not exist in the specified schema. +You can reference a database object inside an SPL program either by its qualified name or by an unqualified name. A qualified name is in the form of `schema.name`, where `schema` is the name of the schema under which the database object with identifier `name` exists. An unqualified name doesn't have the `schema.` portion. When a reference is made to a qualified name, there is no ambiguity as to which database object is intended. It either does or doesn't exist in the specified schema. -Locating an object with an unqualified name, however, requires the use of the current user’s search path. When a user becomes the current user of a session, a default search path is always associated with that user. The search path consists of a list of schemas which are searched in left-to-right order for locating an unqualified database object reference. The object is considered non-existent if it can’t be found in any of the schemas in the search path. The default search path can be displayed in PSQL using the `SHOW search_path` command. +Locating an object with an unqualified name, however, requires the use of the current user’s search path. When a user becomes the current user of a session, a default search path is always associated with that user. The search path consists of a list of schemas that are searched in left-to-right order for locating an unqualified database object reference. The object is considered nonexistent if it can’t be found in any of the schemas in the search path. You can display the default search path in PSQL using the `SHOW search_path` command: ```text edb=# SHOW search_path; @@ -16,9 +16,9 @@ edb=# SHOW search_path; (1 row) ``` -`$user` in the above search path is a generic placeholder that refers to the current user so if the current user of the above session is `enterprisedb`, an unqualified database object would be searched for in the following schemas in this order – first, `enterprisedb`, then `public`. +`$user` in the search path is a generic placeholder that refers to the current user. So if the current user of this session is `enterprisedb`, an unqualified database object is searched for in the following schemas in this order: first in `enterprisedb`, and then in `public`. -Once an unqualified name has been resolved in the search path, it can be determined if the current user has the appropriate privilege to perform the desired action on that specific object. +Once an unqualified name is resolved in the search path, you can determine if the current user has the appropriate privilege to perform the desired action on that specific object. !!! Note - The concept of the search path is not compatible with Oracle databases. For an unqualified reference, Oracle simply looks in the schema of the current user for the named database object. It also important to note that in Oracle, a user and his or her schema is the same entity while in EDB Postgres Advanced Server, a user and a schema are two distinct objects. + The concept of the search path isn't compatible with Oracle databases. For an unqualified reference, Oracle looks in the schema of the current user for the named database object. Also, in Oracle, a user and their schema is the same entity. In EDB Postgres Advanced Server, a user and a schema are two distinct objects. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx index a69bf2b6ba6..cc7e7bb5ff7 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx @@ -4,4 +4,4 @@ title: "Database object privileges" -Once an SPL program begins execution, any attempt to access a database object from within the program results in a check to ensure the current user has the authorization to perform the intended action against the referenced object. Privileges on database objects are bestowed and removed using the `GRANT` and `REVOKE` commands, respectively. If the current user attempts unauthorized access on a database object, then the program throws an exception. See [Exception handling](../../05_control_structures/07_exception_handling/#exception_handling) for information about exception handling. +Once an SPL program begins execution, any attempt to access a database object from the program results in a check. This check ensures that the current user is authorized to perform the intended action against the referenced object. Privileges on database objects are added and removed using the `GRANT` and `REVOKE` commands. If the current user attempts unauthorized access on a database object, then the program throws an exception. See [Exception handling](../../05_control_structures/07_exception_handling/#exception_handling). diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx index 9cbb6bfbc74..546f647f43a 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx @@ -4,18 +4,18 @@ title: "Definer's versus invoker's rights" -When an SPL program is about to begin execution, a determination is made as to what user is to be associated with this process. This user is referred to as the *current user*. The current user’s database object privileges are used to determine whether or not access to database objects referenced in the program is permitted. The current prevailing search path in effect when the program is invoked is used to resolve any unqualified object references. +When an SPL program is about to begin executing, a determination is made as to the user to associate with this process. This user is referred to as the *current user*. The current user’s database object privileges are used to determine whether access to database objects referenced in the program is permitted. The current prevailing search path in effect when the program is invoked is used to resolve any unqualified object references. The selection of the current user is influenced by whether the SPL program was created with definer’s right or invoker’s rights. The `AUTHID` clause determines that selection. Appearance of the clause `AUTHID DEFINER` gives the program definer’s rights. This is also the default if the `AUTHID` clause is omitted. Use of the clause `AUTHID CURRENT_USER` gives the program invoker’s rights. The difference between the two is summarized as follows: -- If a program has *definer’s rights*, then the owner of the program becomes the current user when program execution begins. The program owner’s database object privileges are used to determine if access to a referenced object is permitted. In a definer’s rights program, it is irrelevant as to which user actually invoked the program. -- If a program has *invoker’s rights*, then the current user at the time the program is called remains the current user while the program is executing (but not necessarily within called subprograms – see the following bullet points). When an invoker’s rights program is invoked, the current user is typically the user that started the session (i.e., made the database connection) although it is possible to change the current user after the session has started using the SET ROLE command. In an invoker’s rights program, it is irrelevant as to which user actually owns the program. +- If a program has *definer’s rights*, then the owner of the program becomes the current user when program execution begins. The program owner’s database object privileges are used to determine if access to a referenced object is permitted. In a definer’s rights program, the user who actually invoked the program is irrelevant. +- If a program has *invoker’s rights*, then the current user at the time the program is called remains the current user while the program (but not necessarily the subprogram) is executing. When an invoker’s rights program is invoked, the current user is typically the user that started the session (made the database connection). You can change the current user after the session started using the `SET ROLE` command. In an invoker’s rights program, who actually owns the program is irrelevant. From the previous definitions, the following observations can be made: -- If a definer’s rights program calls a definer’s rights program, the current user changes from the owner of the calling program to the owner of the called program during execution of the called program. -- If a definer’s rights program calls an invoker’s rights program, the owner of the calling program remains the current user during execution of both the calling and called programs. -- If an invoker’s rights program calls an invoker’s rights program, the current user of the calling program remains the current user during execution of the called program. -- If an invokers’ rights program calls a definer’s rights program, the current user switches to the owner of the definer’s rights program during execution of the called program. +- If a definer’s rights program calls a definer’s rights program, the current user changes from the owner of the calling program to the owner of the called program while the called program executes. +- If a definer’s rights program calls an invoker’s rights program, the owner of the calling program remains the current user whiile both the calling and called programs execute. +- If an invoker’s rights program calls an invoker’s rights program, the current user of the calling program remains the current user while the called program executes. +- If an invoker’s rights program calls a definer’s rights program, the current user switches to the owner of the definer’s rights program while the called program executes. -The same principles apply if the called program in turn calls another program in the cases cited above. +The same principles apply if the called program in turn calls another program in these cases. diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx index 54d2836af9d..5fbff0041b5 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx @@ -4,15 +4,15 @@ title: "Security example" -In the following example, a new database is created along with two users: -- `– hr_mgr` who owns a copy of the entire sample application in schema `hr_mgr` -- `sales_mgr` who owns a schema named `sales_mgr` that has a copy of only the `emp` table containing only the employees who work in sales +In this example, a new database is created along with two users: +- `– hr_mgr`, who owns a copy of the entire sample application in schema `hr_mgr` +- `sales_mgr`, who owns a schema named `sales_mgr` that has a copy of only the `emp` table containing only the employees who work in sales -The procedure `list_emp`, function `hire_clerk`, and package `emp_admin` is used in this example. All of the default privileges that are granted upon installation of the sample application are removed and then explicitly re-granted so as to present a more secure environment in this example. +The procedure `list_emp`, function `hire_clerk`, and package `emp_admin` are used in this example. All of the default privileges that are granted upon installation of the sample application are removed and then explicitly regranted so as to present a more secure environment. -Programs `list_emp` and `hire_clerk` are changed from the default of definer’s rights to invoker’s rights. It is then shown that when `sales_mgr` runs these programs, they act upon the `emp` table in the `sales_mgr` schema since the `sales_mgr` search path and privileges are used for name resolution and authorization checking. +Programs `list_emp` and `hire_clerk` are changed from the default of definer’s rights to invoker’s rights. Then, when `sales_mgr` runs these programs, they act on the `emp` table in the `sales_mgr` schema since the `sales_mgr` search path and privileges are used for name resolution and authorization checking. -Programs `get_dept_name` and `hire_emp` in the `emp_admin` package are then executed by `sales_mgr`. In this case, the `dept` table and `emp` table in `hr_mgr`’s schema are accessed as `hr_mgr` is the owner of the `emp_admin` package which is using definer’s rights. Since the default search path is in effect with the `$user` placeholder, the schema matching the user (in this case, `hr_mgr`) is used to find the tables. +Programs `get_dept_name` and `hire_emp` in the `emp_admin` package are then executed by `sales_mgr`. In this case, the `dept` table and `emp` table in the `hr_mgr` schema are accessed as `hr_mgr` is the owner of the `emp_admin` package which is using definer’s rights. Since the default search path is in effect with the `$user` placeholder, the schema matching the user (in this case, `hr_mgr`) is used to find the tables. ## Step 1: Create database and users @@ -32,7 +32,7 @@ CREATE USER sales_mgr IDENTIFIED BY password; ## Step 2: Create the sample application -Create the entire sample application, owned by `hr_mgr`, in `hr_mgr`’s schema. +Create the entire sample application, owned by `hr_mgr`, in the `hr_mgr` schema. ```text \c - hr_mgr @@ -54,7 +54,7 @@ COMMIT ## Step 3: Create the emp table in schema sales_mgr -Create a subset of the `emp` table owned by `sales_mgr` in `sales_mgr`’s schema. +Create a subset of the `emp` table owned by `sales_mgr` in the `sales_mgr` schema. ```text \c – hr_mgr @@ -63,7 +63,7 @@ GRANT USAGE ON SCHEMA hr_mgr TO sales_mgr; CREATE TABLE emp AS SELECT * FROM hr_mgr.emp WHERE job = 'SALESMAN'; ``` -In the above example, the `GRANT USAGE ON SCHEMA` command is given to allow `sales_mgr` access into `hr_mgr`’s schema to make a copy of `hr_mgr`’s `emp` table. This step is required in EDB Postgres Advanced Server and is not compatible with Oracle databases since Oracle does not have the concept of a schema that is distinct from its user. +The `GRANT USAGE ON SCHEMA` command allows `sales_mgr` access into the `hr_mgr`’s schema to make a copy of the `hr_mgr` `emp` table. This step is required in EDB Postgres Advanced Server and isn't compatible with Oracle databases. Oracle doesn't have the concept of a schema that's distinct from its user. ## Step 4: Remove default privileges @@ -83,7 +83,7 @@ REVOKE EXECUTE ON PACKAGE emp_admin FROM PUBLIC; ## Step 5: Change list_emp to invoker’s rights -While connected as user, `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `list_emp` program and resave it in EDB Postgres Advanced Server. When performing this step, be sure you are logged on as `hr_mgr`, otherwise the modified program may wind up in the `public` schema instead of in `hr_mgr`’s schema. +While connected as user `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `list_emp` program and resave it in EDB Postgres Advanced Server. When performing this step, be sure you're logged in as `hr_mgr`. Otherwise the modified program might end up in the `public` schema instead of in the `hr_mgr` schema. ```text CREATE OR REPLACE PROCEDURE list_emp @@ -108,11 +108,11 @@ END; ## Step 6: Change hire_clerk to invoker’s rights and qualify call to new_empno -While connected as user, `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `hire_clerk` program. +While connected as user `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `hire_clerk` program. -Also, after the `BEGIN` statement, fully qualify the reference, `new_empno`, to `hr_mgr.new_empno` in order to ensure the `hire_clerk` function call to the `new_empno` function resolves to the `hr_mgr` schema. +Also, after the `BEGIN` statement, fully qualify the reference `new_empno` to `hr_mgr.new_empno` to ensure the `hire_clerk` function call to the `new_empno` function resolves to the `hr_mgr` schema. -When resaving the program, be sure you are logged on as `hr_mgr`, otherwise the modified program may wind up in the `public` schema instead of in `hr_mgr`’s schema. +When resaving the program, be sure you're logged in as `hr_mgr`. Otherwise the modified program might end up in the `public` schema instead of in the `hr_mgr` schema. ```text CREATE OR REPLACE FUNCTION hire_clerk ( @@ -157,7 +157,7 @@ END; ## Step 7: Grant required privileges -While connected as user, `hr_mgr`, grant the privileges needed so `sales_mgr` can execute the `list_emp` procedure, `hire_clerk` function, and `emp_admin` package. Note that the only data object `sales_mgr` has access to is the `emp` table in the `sales_mgr` schema. `sales_mgr` has no privileges on any table in the `hr_mgr` schema. +While connected as user `hr_mgr`, grant the privileges needed so `sales_mgr` can execute the `list_emp` procedure, `hire_clerk` function, and `emp_admin` package. The only data object `sales_mgr` has access to is the `emp` table in the `sales_mgr` schema. `sales_mgr` has no privileges on any table in the `hr_mgr` schema. ```text GRANT USAGE ON SCHEMA hr_mgr TO sales_mgr; @@ -169,7 +169,7 @@ GRANT EXECUTE ON PACKAGE emp_admin TO sales_mgr; ## Step 8: Run programs list_emp and hire_clerk** -Connect as user, `sales_mgr`, and run the following anonymous block: +Connect as user `sales_mgr`, and run the following anonymous block: ```text \c – sales_mgr @@ -207,13 +207,13 @@ EMPNO ENAME 8000 JONES ``` -The table and sequence accessed by the programs of the anonymous block are illustrated in the following diagram. The gray ovals represent the schemas of `sales_mgr` and `hr_mgr`. The current user during each program execution is shown within parenthesis in bold red font. +The table and sequence accessed by the programs of the anonymous block are shown in the following diagram. The gray ovals represent the schemas of `sales_mgr` and `hr_mgr`. The current user during each program execution is shown in parenthesis in bold red font. ![Invokers Rights Programs](../../images/invokers_rights_programs.png)
Fig. 1: Invokers Rights Programs
-Selecting from `sales_mgr`’s `emp` table shows that the update was made in this table. +Selecting from the `sales_mgr` `emp` table shows that the update was made in this table. ```text SELECT empno, ename, hiredate, sal, deptno, @@ -229,7 +229,7 @@ hr_mgr.emp_admin.get_dept_name(deptno) FROM sales_mgr.emp; (5 rows) ``` -The following diagram shows that the `SELECT` command references the `emp` table in the `sales_mgr` schema, but the `dept` table referenced by the `get_dept_name` function in the `emp_admin` package is from the `hr_mgr` schema since the `emp_admin` package has definer’s rights and is owned by `hr_mgr`. The default search path setting with the `$user` placeholder resolves the access by user `hr_mgr` to the `dept` table in the `hr_mgr` schema. +The following diagram shows that the `SELECT` command references the `emp` table in the `sales_mgr` schema. However, the `dept` table referenced by the `get_dept_name` function in the `emp_admin` package is from the `hr_mgr` schema since the `emp_admin` package has definer’s rights and is owned by `hr_mgr`. The default search path setting with the `$user` placeholder resolves the access by user `hr_mgr` to the `dept` table in the `hr_mgr` schema. ![Definer's Rights Package](../../images/definers_rights_package.png) @@ -237,20 +237,20 @@ The following diagram shows that the `SELECT` command references the `emp` table ## Step 9: Run program hire_emp in the emp_admin package -While connected as user, `sales_mgr`, run the `hire_emp` procedure in the `emp_admin` package. +While connected as user `sales_mgr`, run the `hire_emp` procedure in the `emp_admin` package. ```text EXEC hr_mgr.emp_admin.hire_emp(9001, 'ALICE','SALESMAN',8000,TRUNC(SYSDATE),1000,7369,40); ``` -This diagram illustrates that the `hire_emp` procedure in the `emp_admin` definer’s rights package updates the `emp` table belonging to `hr_mgr` since the object privileges of `hr_mgr` are used, and the default search path setting with the `$user` placeholder resolves to the schema of `hr_mgr`. +This diagram shows that the `hire_emp` procedure in the `emp_admin` definer’s rights package updates the `emp` table belonging to `hr_mgr`. The object privileges of `hr_mgr` are used and the default search path setting with the `$user` placeholder resolves to the schema of `hr_mgr`. ![Definer's Rights Package](../../images/definer's_rights_package.png)
Fig. 3: Definer's Rights Package
-Now connect as user, `hr_mgr`. The following `SELECT` command verifies that the new employee was added to `hr_mgr`’s `emp` table since the `emp_admin` package has definer’s rights and `hr_mgr` is `emp_admin`’s owner. +Now connect as user `hr_mgr`. The following `SELECT` command verifies that the new employee was added to the `hr_mgr` `emp` table since the `emp_admin` package has definer’s rights and `hr_mgr` is the `emp_admin` owner. ```text \c – hr_mgr diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/index.mdx index 32d6379ae28..fdaf90d4bdd 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/09_program_security/index.mdx @@ -8,13 +8,11 @@ legacyRedirectsGenerated: -Security over what user may execute an SPL program and what database objects an SPL program may access for any given user executing the program is controlled by the following: +You can control the security over whether a user can execute an SPL program. You can also control the database objects an SPL program can access for any given user executing the program. These are controlled by the following: -- Privilege to execute a program. -- Privileges granted on the database objects (including other SPL programs) which a program attempts to access. -- Whether the program is defined with definer’s rights or invoker’s rights. - -These aspects are discussed in the following sections. +- Privilege to execute a program +- Privileges granted on the database objects (including other SPL programs) that a program attempts to access +- Whether the program is defined with definer’s rights or invoker’s rights
From f9b201378cfe8e2761c8eaf2a9e739b4e8821eaf Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 10:19:27 -0400 Subject: [PATCH 08/32] All changes for standardized URLs for JDBC except deploy.mjs --- .../ibm_power_ppc64le/index.mdx | 15 --------- .../index.mdx | 30 ----------------- .../x86_amd64/index.mdx | 31 ----------------- .../docs/jdbc_connector/42.5.0.1/index.mdx | 13 ++++++++ .../configuring_for_java.mdx} | 2 ++ .../index.mdx | 28 +++++++++++++++- .../installing/linux_ppc64le/index.mdx | 17 ++++++++++ .../linux_ppc64le/jdbc_rhel_8.mdx} | 0 .../linux_ppc64le/jdbc_sles_12.mdx} | 0 .../linux_ppc64le/jdbc_sles_15.mdx} | 0 .../installing/linux_x86_64/index.mdx | 33 +++++++++++++++++++ .../linux_x86_64/jdbc_centos_7.mdx} | 0 .../linux_x86_64/jdbc_deb_10.mdx} | 0 .../linux_x86_64/jdbc_deb_11.mdx} | 0 .../linux_x86_64/jdbc_other_linux_8.mdx} | 0 .../linux_x86_64/jdbc_rhel_7.mdx} | 0 .../linux_x86_64/jdbc_rhel_8.mdx} | 0 .../linux_x86_64/jdbc_sles_12.mdx} | 0 .../linux_x86_64/jdbc_sles_15.mdx} | 0 .../linux_x86_64/jdbc_ubuntu_18.mdx} | 0 .../linux_x86_64/jdbc_ubuntu_20.mdx} | 0 .../upgrading.mdx} | 3 ++ .../windows.mdx} | 5 +-- 23 files changed, 98 insertions(+), 79 deletions(-) delete mode 100644 product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx delete mode 100644 product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx delete mode 100644 product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx => installing/configuring_for_java.mdx} (89%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector => installing}/index.mdx (50%) create mode 100644 product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx => installing/linux_ppc64le/jdbc_rhel_8.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx => installing/linux_ppc64le/jdbc_sles_12.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx => installing/linux_ppc64le/jdbc_sles_15.mdx} (100%) create mode 100644 product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx => installing/linux_x86_64/jdbc_centos_7.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx => installing/linux_x86_64/jdbc_deb_10.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb11_x86.mdx => installing/linux_x86_64/jdbc_deb_11.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx => installing/linux_x86_64/jdbc_other_linux_8.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx => installing/linux_x86_64/jdbc_rhel_7.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx => installing/linux_x86_64/jdbc_rhel_8.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx => installing/linux_x86_64/jdbc_sles_12.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx => installing/linux_x86_64/jdbc_sles_15.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx => installing/linux_x86_64/jdbc_ubuntu_18.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx => installing/linux_x86_64/jdbc_ubuntu_20.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx => installing/upgrading.mdx} (85%) rename product_docs/docs/jdbc_connector/42.5.0.1/{04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx => installing/windows.mdx} (94%) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx deleted file mode 100644 index 53faec2f868..00000000000 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: "Installing EDB JDBC Connector on IBM Power (ppc64le)" -navTitle: "IBM Power (ppc64le)" -navigation: -- jdbc42_rhel8_ppcle -- jdbc42_sles15_ppcle -- jdbc42_sles12_ppcle ---- - -For operating system-specific install instructions, see: - - - [RHEL 8](jdbc42_rhel8_ppcle) - - - [SLES 15](jdbc42_sles15_ppcle) - - [SLES 12](jdbc42_sles12_ppcle) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx deleted file mode 100644 index 4fe3e94ba91..00000000000 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "Installing EDB JDBC Connector on Linux" -navTitle: "Installing on Linux" -navigation: -- x86_amd64 -- ibm_power_ppc64le ---- - -To install EDB JDBC Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). - -For platform-specific install instructions, see: - -- Linux x86-64 (amd64): - - [RHEL 8/OL 8](x86_amd64/jdbc42_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](x86_amd64/jdbc42_other_linux8_x86) - - [RHEL 7/OL 7](x86_amd64/jdbc42_rhel7_x86) - - [CentOS 7](x86_amd64/jdbc42_centos7_x86) - - [SLES 15](x86_amd64/jdbc42_sles15_x86) - - [SLES 12](x86_amd64/jdbc42_sles12_x86) - - [Ubuntu 20.04](x86_amd64/jdbc42_ubuntu20_x86) - - [Ubuntu 18.04](x86_amd64/jdbc42_ubuntu18_x86) - - [Debian 11](x86_amd64/jdbc42_deb11_x86) - - [Debian 10](x86_amd64/jdbc42_deb10_x86) - -- Linux on IBM Power (ppc64le): - - [RHEL 8](ibm_power_ppc64le/jdbc42_rhel8_ppcle) - - - [SLES 15](ibm_power_ppc64le/jdbc42_sles15_ppcle) - - [SLES 12](ibm_power_ppc64le/jdbc42_sles12_ppcle) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx deleted file mode 100644 index 123caff8781..00000000000 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Installing EDB JDBC Connector on Linux x86 (amd64)" -navTitle: "Intel x86 (amd64)" -navigation: -- jdbc42_rhel8_x86 -- jdbc42_other_linux8_x86 -- jdbc42_rhel7_x86 -- jdbc42_centos7_x86 -- jdbc42_sles15_x86 -- jdbc42_sles12_x86 -- jdbc42_ubuntu22_x86 -- jdbc42_ubuntu20_x86 -- jdbc42_ubuntu18_x86 -- jdbc42_deb11_x86 -- jdbc42_deb10_x86 ---- - -For operating system-specific install instructions, see: - - - [RHEL 8/OL 8](jdbc42_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](jdbc42_other_linux8_x86) - - [RHEL 7/OL 7](jdbc42_rhel7_x86) - - [CentOS 7](jdbc42_centos7_x86) - - [SLES 15](jdbc42_sles15_x86) - - [SLES 12](jdbc42_sles12_x86) - - [Ubuntu 20.04](jdbc42_ubuntu20_x86) - - [Ubuntu 18.04](jdbc42_ubuntu18_x86) - - [Debian 11](jdbc42_deb11_x86) - - [Debian 10](jdbc42_deb10_x86) - diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/index.mdx index 3ba098e8793..b8adfec3b27 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/index.mdx @@ -2,6 +2,19 @@ title: "EDB JDBC Connector" directoryDefaults: description: "EDB JDBC Connector Version 42.2.12.3 Documentation and release notes." +navigation: +- 01_jdbc_rel_notes +- 02_requirements_overview +- 03_advanced_server_jdbc_connector_overview +- installing +- 05_using_the_advanced_server_jdbc_connector_with_java_applications +- 05a_using_advanced_queueing +- 06_executing_sql_commands_with_executeUpdate() +- 07_adding_a_graphical_interface_to_a_java_program +- 08_advanced_jdbc_connector_functionality +- 09_security_and_encryption +- 10_advanced_server_jdbc_connector_logging +- 11_reference_jdbc_data_types legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/configuring_for_java.mdx similarity index 89% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/configuring_for_java.mdx index 54ef7f4a396..b05c58f0017 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/configuring_for_java.mdx @@ -1,6 +1,8 @@ --- title: "Configuring EDB JDBC Connector for Java" navTitle: "Configuring for Java" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx similarity index 50% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index 0a7d34a8b5a..80abb7c399c 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -1,7 +1,16 @@ --- title: "Installing and configuring EDB JDBC Connector" -navTitle: "Installing and configuring" +navTitle: "Installing" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package +navigation: +- linux_x86_64 +- linux_ppc64le +- windows +- configuring_for_java +- upgrading legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/installing_and_configuring_the_jdbc_connector.html" @@ -17,3 +26,20 @@ Before installing the EDB JDBC Connector, you must have Java installed on your s You can use the EDB Postgres Advanced Server graphical installer or an RPM package to add the EDB JDBC Connector to your installation. +## [Linux x86-64 (amd64)](linux_x86_64) +### Red Hat Enterprise Linux (RHEL) family +- [RHEL 8](linux_x86_64/jdbc_rhel_8), [RHEL 7](linux_x86_64/jdbc_rhel_7) +- [Oracle Linux (OL) 8](linux_x86_64/jdbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/jdbc_rhel_7) +- [Rocky Linux 8](linux_x86_64/jdbc_other_linux_8) +- [AlmaLinux 8](linux_x86_64/jdbc_other_linux_8) +- [CentOS 7](linux_x86_64/jdbc_centos_7) +### SUSE Linux Enterprise (SLES) family +- [SLES 15](linux_x86_64/jdbc_sles_15), [SLES 12](linux_x86_64/jdbc_sles_12) +### Debian family +- [Ubuntu 20.04](linux_x86_64/jdbc_ubuntu_20), [Ubuntu 18.04](linux_x86_64/jdbc_ubuntu_18) +- [Debian 11](linux_x86_64/jdbc_deb_11), [Debian 10](linux_x86_64/jdbc_deb_10) +## [Linux on IBM Power (ppc64le)](linux_ppc64le) +### Red Hat Enterprise Linux (RHEL) family +- [RHEL 8](linux_ppc64le/jdbc_rhel_8) +### SUSE Linux Enterprise (SLES) family +- [SLES 15](linux_ppc64le/jdbc_sles_15), [SLES 12](linux_ppc64le/jdbc_sles_12) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx new file mode 100644 index 00000000000..3a9547b1580 --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx @@ -0,0 +1,17 @@ +--- +title: "Installing EDB JDBC Connector on IBM Power (ppc64le)" +navTitle: "On Linux ppc64le" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le +navigation: +- jdbc_rhel_8 +- jdbc_sles_15 +- jdbc_sles_12 +--- + +For operating system-specific install instructions, see: + + - [RHEL 8](jdbc_rhel_8) + + - [SLES 15](jdbc_sles_15) + - [SLES 12](jdbc_sles_12) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx new file mode 100644 index 00000000000..4018429a010 --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx @@ -0,0 +1,33 @@ +--- +title: "Installing EDB JDBC Connector on Linux x86 (amd64)" +navTitle: "On Linux x86" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64 +navigation: +- jdbc_rhel_8 +- jdbc_other_linux_8 +- jdbc_rhel_7 +- jdbc_centos_7 +- jdbc_sles_15 +- jdbc_sles_12 +- jdbc_ubuntu_22 +- jdbc_ubuntu_20 +- jdbc_ubuntu_18 +- jdbc_deb_11 +- jdbc_deb_10 +--- + +For operating system-specific install instructions, see: + + - [RHEL 8/OL 8](jdbc_rhel_8) + + - [Rocky Linux 8/AlmaLinux 8](jdbc_other_linux_8) + - [RHEL 7/OL 7](jdbc_rhel_7) + - [CentOS 7](jdbc_centos_7) + - [SLES 15](jdbc_sles_15) + - [SLES 12](jdbc_sles_12) + - [Ubuntu 20.04](jdbc_ubuntu_20) + - [Ubuntu 18.04](jdbc_ubuntu_18) + - [Debian 11](jdbc_deb_11) + - [Debian 10](jdbc_deb_10) + diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb11_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb11_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/upgrading.mdx similarity index 85% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/upgrading.mdx index 1a9e00ba1ac..797c9b7302f 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/upgrading.mdx @@ -1,5 +1,8 @@ --- title: Upgrading a Linux installation +navTitle: "Upgrading" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install --- If you have an existing JDBC Connector RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx similarity index 94% rename from product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx index 39027e39d09..b7d3fb7d112 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx @@ -1,7 +1,8 @@ --- title: "Installing EDB JDBC Connector on Windows" -navTitle: "Installing on Windows" - +navTitle: "On Windows" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/using_the_graphical_installer_to_install_the_connector.html" From d09c5088a4b7aaed63a320deb9f83576e8a29125 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 10:27:08 -0400 Subject: [PATCH 09/32] Modified template for JDBC to add prerequisite of ensuring that Java is installed. Removed the same instruction from master Installing index page. --- .../templates/products/edb-jdbc-connector/base.njk | 2 ++ .../docs/jdbc_connector/42.5.0.1/installing/index.mdx | 5 ----- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/install_template/templates/products/edb-jdbc-connector/base.njk b/install_template/templates/products/edb-jdbc-connector/base.njk index ad29f74fea0..ac0b0ac4ffa 100644 --- a/install_template/templates/products/edb-jdbc-connector/base.njk +++ b/install_template/templates/products/edb-jdbc-connector/base.njk @@ -2,6 +2,8 @@ {% set packageName %}edb-jdbc{% endset %} {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). {% endblock prodprereq %} diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index 80abb7c399c..2764fe169c5 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -21,11 +21,6 @@ legacyRedirectsGenerated: -Before installing the EDB JDBC Connector, you must have Java installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. - -You can use the EDB Postgres Advanced Server graphical installer or an RPM package to add the EDB JDBC Connector to your installation. - - ## [Linux x86-64 (amd64)](linux_x86_64) ### Red Hat Enterprise Linux (RHEL) family - [RHEL 8](linux_x86_64/jdbc_rhel_8), [RHEL 7](linux_x86_64/jdbc_rhel_7) From d03dcd23a631bccd05c8d4148908ee84046424d1 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 11:10:57 -0400 Subject: [PATCH 10/32] Revised deploy.mjs for JDBC and updated text for install topics to include Java prerequisite --- install_template/deploy.mjs | 22 +++++++++---------- .../installing/linux_ppc64le/jdbc_rhel_8.mdx | 2 ++ .../installing/linux_ppc64le/jdbc_sles_12.mdx | 2 ++ .../installing/linux_ppc64le/jdbc_sles_15.mdx | 2 ++ .../installing/linux_x86_64/jdbc_centos_7.mdx | 2 ++ .../installing/linux_x86_64/jdbc_deb_10.mdx | 2 ++ .../installing/linux_x86_64/jdbc_deb_11.mdx | 2 ++ .../linux_x86_64/jdbc_other_linux_8.mdx | 2 ++ .../installing/linux_x86_64/jdbc_rhel_7.mdx | 2 ++ .../installing/linux_x86_64/jdbc_rhel_8.mdx | 2 ++ .../installing/linux_x86_64/jdbc_sles_12.mdx | 2 ++ .../installing/linux_x86_64/jdbc_sles_15.mdx | 2 ++ .../linux_x86_64/jdbc_ubuntu_18.mdx | 2 ++ .../linux_x86_64/jdbc_ubuntu_20.mdx | 2 ++ 14 files changed, 37 insertions(+), 11 deletions(-) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index c1ca0ca24cf..94fae7fc2be 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -270,27 +270,27 @@ const moveDoc = async (product, platform, version) => { (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_centos7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_centos_7.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_other_linux8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_other_linux_8.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_7.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_8.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_8.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles12_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_sles_12.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles15_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_sles_15.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_deb10_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_deb_10.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_deb11_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_deb_11.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_18.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_20.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`), diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx index 471c281aa6c..e0b03d4085d 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx index dae590b488c..084b973f6e4 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx index 3c31b252290..4358009b71e 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx index 61ed8bd8821..1c1cbabdf5e 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx index e5f2d94ba12..6445b75c35f 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx index 5774c1db8d7..513c2aeeccd 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx index 37bdca82bd0..59ec01bcae1 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx index 13fe62f1221..57b5f91efe7 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx index 33f9a39a048..c1abcb02423 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx index 193a0a85a87..59df87fbb1b 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx index a3a9da9b602..4ead1a556ee 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx index 03b4455f0fc..e637847950b 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx index 04590396076..4b435c83e7b 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx @@ -13,6 +13,8 @@ Before you begin the installation process: - Install EDB Postgres Advanced Server on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See [Installing EDB Postgres Advanced Server](/epas/latest/epas_inst_linux). +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + - Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). - Set up the repository From e380db5dc10547c81221b6eb6ba325a379ca4ce4 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 12:12:33 -0400 Subject: [PATCH 11/32] Changes to implement standardized URLs for OCL except deploy.mjs --- .../index.mdx | 12 ------- .../ibm_power_ppc64le/index.mdx | 16 --------- .../install_on_linux_using_edb_repo/index.mdx | 31 ---------------- .../x86_amd64/index.mdx | 33 ----------------- .../docs/ocl_connector/14.1.0.1/index.mdx | 9 +++++ .../14.1.0.1/installing/index.mdx | 29 +++++++++++++++ .../installing/linux_ppc64le/index.mdx | 17 +++++++++ .../linux_ppc64le/ocl_connector_rhel_8.mdx} | 0 .../linux_ppc64le/ocl_connector_sles_12.mdx} | 0 .../linux_ppc64le/ocl_connector_sles_15.mdx} | 0 .../installing/linux_x86_64/index.mdx | 35 +++++++++++++++++++ .../linux_x86_64/ocl_connector_centos_7.mdx} | 0 .../linux_x86_64/ocl_connector_deb_10.mdx} | 0 .../linux_x86_64/ocl_connector_deb_11.mdx} | 0 .../ocl_connector_other_linux_8.mdx} | 0 .../linux_x86_64/ocl_connector_rhel_7.mdx} | 0 .../linux_x86_64/ocl_connector_rhel_8.mdx} | 0 .../linux_x86_64/ocl_connector_sles_12.mdx} | 0 .../linux_x86_64/ocl_connector_sles_15.mdx} | 0 .../linux_x86_64/ocl_connector_ubuntu_18.mdx} | 0 .../linux_x86_64/ocl_connector_ubuntu_20.mdx} | 0 .../upgrading.mdx} | 5 ++- .../windows.mdx} | 16 +++++---- 23 files changed, 103 insertions(+), 100 deletions(-) delete mode 100644 product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/index.mdx delete mode 100644 product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx delete mode 100644 product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx delete mode 100644 product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx create mode 100644 product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx create mode 100644 product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx => installing/linux_ppc64le/ocl_connector_rhel_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx => installing/linux_ppc64le/ocl_connector_sles_12.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx => installing/linux_ppc64le/ocl_connector_sles_15.mdx} (100%) create mode 100644 product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx => installing/linux_x86_64/ocl_connector_centos_7.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx => installing/linux_x86_64/ocl_connector_deb_10.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb11_x86.mdx => installing/linux_x86_64/ocl_connector_deb_11.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx => installing/linux_x86_64/ocl_connector_other_linux_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx => installing/linux_x86_64/ocl_connector_rhel_7.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx => installing/linux_x86_64/ocl_connector_rhel_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx => installing/linux_x86_64/ocl_connector_sles_12.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx => installing/linux_x86_64/ocl_connector_sles_15.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx => installing/linux_x86_64/ocl_connector_ubuntu_18.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx => installing/linux_x86_64/ocl_connector_ubuntu_20.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install.mdx => installing/upgrading.mdx} (80%) rename product_docs/docs/ocl_connector/14.1.0.1/{04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows.mdx => installing/windows.mdx} (73%) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/index.mdx deleted file mode 100644 index a06f19195c0..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/index.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "Installing and configuring EDB OCL Connector" -navigation: -- install_on_linux_using_edb_repo -- install_on_windows -- 11_updating_rpm_install ---- - -You can install the OCL Connector on: - -- [Linux x86-64 (amd64) and IBM Power (ppc64le)](install_on_linux_using_edb_repo) -- [Windows x86-64](install_on_windows) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx deleted file mode 100644 index dcafdf97bad..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/index.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Installing EDB OCL Connector on IBM Power (ppc64le)" -navTitle: "IBM Power (ppc64le)" -navigation: -- ocl_connector14_rhel8_ppcle -- ocl_connector14_sles15_ppcle -- ocl_connector14_sles12_ppcle ---- - -For operating system-specific install instructions, see: - - - - [RHEL 8](ocl_connector14_rhel8_ppcle) - - - [SLES 15](ocl_connector14_sles15_ppcle) - - [SLES 12](ocl_connector14_sles12_ppcle) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx deleted file mode 100644 index 10ed055d78e..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/index.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Installing on Linux" -navTitle: "Linux" -navigation: -- x86_amd64 -- ibm_power_ppc64le ---- - -To install EDB OCL Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). - -For platform-specific install instructions, see: - -- Linux x86-64 (amd64): - - [RHEL 8/OL 8](x86_amd64/ocl_connector14_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](x86_amd64/ocl_connector14_other_linux8_x86) - - - [RHEL 7/OL 7](x86_amd64/ocl_connector14_rhel7_x86) - - [CentOS 7](x86_amd64/ocl_connector14_centos7_x86) - - [SLES 15](x86_amd64/ocl_connector14_sles15_x86) - - [SLES 12](x86_amd64/ocl_connector14_sles12_x86) - - [Ubuntu 20.04](x86_amd64/ocl_connector14_ubuntu20_x86) - - [Ubuntu 18.04](x86_amd64/ocl_connector14_ubuntu18_x86) - - [Debian 11](x86_amd64/ocl_connector14_deb11_x86) - - [Debian 10](x86_amd64/ocl_connector14_deb10_x86) - -- Linux on IBM Power (ppc64le): - - [RHEL 8](ibm_power_ppc64le/ocl_connector14_rhel8_ppcle) - - - [SLES 15](ibm_power_ppc64le/ocl_connector14_sles15_ppcle) - - [SLES 12](ibm_power_ppc64le/ocl_connector14_sles12_ppcle) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx deleted file mode 100644 index 0ca6125ff7a..00000000000 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/index.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "Installing EDB OCL Connector on Linux x86 (amd64)" -navTitle: "Intel x86 (amd64)" -navigation: -- ocl_connector14_rhel8_x86 -- ocl_connector14_other_linux8_x86 -- ocl_connector14_rhel7_x86 -- ocl_connector14_centos7_x86 -- ocl_connector14_sles15_x86 -- ocl_connector14_sles12_x86 -- ocl_connector14_ubuntu22_x86 -- ocl_connector14_ubuntu20_x86 -- ocl_connector14_ubuntu18_x86 -- ocl_connector14_deb11_x86 -- ocl_connector14_deb10_x86 ---- - -For operating system-specific install instructions, see: - - - - [RHEL 8/OL 8](ocl_connector14_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](ocl_connector14_other_linux8_x86) - - [RHEL 7/OL 8](ocl_connector14_rhel7_x86) - - [RHEL CentOS 7](ocl_connector14_centos7_x86) - - [SLES 15](ocl_connector14_sles15_x86) - - [SLES 12](ocl_connector14_sles12_x86) - - [Ubuntu 20.04](ocl_connector14_ubuntu20_x86) - - [Ubuntu 18.04](ocl_connector14_ubuntu18_x86) - - [Debian 11](ocl_connector14_deb11_x86) - - [Debian 10](ocl_connector14_deb10_x86) - - diff --git a/product_docs/docs/ocl_connector/14.1.0.1/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/index.mdx index cf61a00efe9..2686ecf6a18 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/index.mdx @@ -2,6 +2,15 @@ title: "EDB OCL Connector" directoryDefaults: description: "EDB OCL Connector Version 14.1.0.1 Documentation and release notes." +navigation: +- 01_ocl_release_notes +- 02_supported_platforms +- 03_libpq_compatibility +- installing +- 04_open_client_library +- 05_generating_the_ocl_trace +- 06_using_ssl +- 07_scram_compatibility --- The EDB OCL Connector provides an API similar to the Oracle Call Interface. You can use EDB's OCL Connector to compile applications that are written to use the Oracle Call Interface to interact with an EDB Postgres Advanced Server database server. diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx new file mode 100644 index 00000000000..287231bada6 --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -0,0 +1,29 @@ +--- +title: "Installing" +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector +navigation: +- linux_x86_64 +- linux_ppc64le +- windows +- upgrading +--- + +## [Linux x86-64 (amd64)](linux_x86_64) +### Red Hat Enterprise Linux (RHEL) family +- [RHEL 8](linux_x86_64/ocl_connector_rhel_8), [RHEL 7](linux_x86_64/ocl_connector_rhel_7) +- [Oracle Linux (OL) 8](linux_x86_64/ocl_connector_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_connector_rhel_7) +- [Rocky Linux 8](linux_x86_64/ocl_connector_other_linux_8) +- [AlmaLinux 8](linux_x86_64/ocl_connector_other_linux_8) +- [CentOS 7](linux_x86_64/ocl_connector_centos_7) +### SUSE Linux Enterprise (SLES) family +- [SLES 15](linux_x86_64/ocl_connector_sles_15), [SLES 12](linux_x86_64/ocl_connector_sles_12) +### Debian family +- [Ubuntu 20.04](linux_x86_64/ocl_connector_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_connector_ubuntu_18) +- [Debian 11](linux_x86_64/ocl_connector_deb_11), [Debian 10](linux_x86_64/ocl_connector_deb_10) +## [Linux on IBM Power (ppc64le)](linux_ppc64le) +### Red Hat Enterprise Linux (RHEL) family +- [RHEL 8](linux_ppc64le/ocl_connector_rhel_8) +### SUSE Linux Enterprise (SLES) family +- [SLES 15](linux_ppc64le/ocl_connector_sles_15), [SLES 12](linux_ppc64le/ocl_connector_sles_12) +## [Windows](windows) \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx new file mode 100644 index 00000000000..affec384909 --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx @@ -0,0 +1,17 @@ +--- +title: "Installing EDB OCL Connector on IBM Power (ppc64le)" +navTitle: "On Linux ppc64le" +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le +navigation: +- ocl_connector_rhel_8 +- ocl_connector_sles_15 +- ocl_connector_sles_12 +--- + +For operating system-specific install instructions, see: + + - [RHEL 8](ocl_connector_rhel_8) + + - [SLES 15](ocl_connector_sles_15) + - [SLES 12](ocl_connector_sles_12) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_rhel_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_rhel8_ppcle.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_rhel_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_12.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles12_ppcle.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_12.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_15.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_connector14_sles15_ppcle.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_15.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx new file mode 100644 index 00000000000..4d5c6e7c4ca --- /dev/null +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx @@ -0,0 +1,35 @@ +--- +title: "Installing EDB OCL Connector on Linux x86 (amd64)" +navTitle: "On Linux x86" +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64 +navigation: +- ocl_connector_rhel_8 +- ocl_connector_other_linux_8 +- ocl_connector_rhel_7 +- ocl_connector_centos_7 +- ocl_connector_sles_15 +- ocl_connector_sles_12 +- ocl_connector_ubuntu_22 +- ocl_connector_ubuntu_20 +- ocl_connector_ubuntu_18 +- ocl_connector_deb_11 +- ocl_connector_deb_10 +--- + +For operating system-specific install instructions, see: + + + - [RHEL 8/OL 8](ocl_connector_rhel_8) + + - [Rocky Linux 8/AlmaLinux 8](ocl_connector_other_linux_8) + - [RHEL 7/OL 8](ocl_connector_rhel_7) + - [RHEL CentOS 7](ocl_connector_centos_7) + - [SLES 15](ocl_connector_sles_15) + - [SLES 12](ocl_connector_sles_12) + - [Ubuntu 20.04](ocl_connector_ubuntu_20) + - [Ubuntu 18.04](ocl_connector_ubuntu_18) + - [Debian 11](ocl_connector_deb_11) + - [Debian 10](ocl_connector_deb_10) + + diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_centos_7.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_centos7_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_centos_7.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_10.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb10_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_10.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb11_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_11.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_deb11_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_11.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_other_linux_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_other_linux8_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_other_linux_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_7.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel7_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_7.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_rhel8_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_12.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles12_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_12.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_15.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_sles15_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_15.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_18.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu18_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_18.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_20.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_connector14_ubuntu20_x86.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_20.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx similarity index 80% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx index 8941ce5a5b1..f5aedc40a38 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx @@ -1,5 +1,8 @@ --- -title: "Updating a Linux installation" +title: "Upgrading a Linux installation" +navTitle: "Upgrading" +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install --- If you have an existing `OCL Connector` RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx similarity index 73% rename from product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx index 626adb21b2a..5dbf6567dd8 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx @@ -1,6 +1,8 @@ --- title: "Installing on Windows" -navTitle: "Windows" +navTitle: "On Windows" +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows --- @@ -10,25 +12,25 @@ This section demonstrates using the Installation Wizard to install the Connector When the `Language Selection` popup opens, select an installation language and click `OK` to continue to the `Setup` window. -![The OCL Connector Installation wizard](../../images/ocl_installation_wizard.png) +![The OCL Connector Installation wizard](../images/ocl_installation_wizard.png) The OCL Connector Installation wizard Click `Next` to continue. -![The Installation dialog](../../images/ocl_installation_dialog.png) +![The Installation dialog](../images/ocl_installation_dialog.png) The Installation dialog Use the `Installation Directory` dialog to specify the directory in which the connector will be installed, and click `Next` to continue. -![The Ready to Install dialog](../../images/ready_to_install.png) +![The Ready to Install dialog](../images/ready_to_install.png) The Ready to Install dialog Click `Next` on the `Ready to Install` dialog to start the installation; popup dialogs confirm the progress of the installation wizard. -![The installation is complete](../../images/ocl_installation_complete.png) +![The installation is complete](../images/ocl_installation_complete.png) The installation is complete @@ -36,13 +38,13 @@ When the wizard informs you that it has completed the setup, click the `Finish` You can also use StackBuilder Plus to add or update the connector on an existing Advanced Server installation; to open StackBuilder Plus, select StackBuilder Plus from the Windows `Apps` menu. -![Starting StackBuilder Plus](../../images/starting_stackbuilder_plus.png) +![Starting StackBuilder Plus](../images/starting_stackbuilder_plus.png) Starting StackBuilder Plus When StackBuilder Plus opens, follow the onscreen instructions. Select the `EnterpriseDB OCI Connector` option from the `Database Drivers` node of the tree control. -![Selecting the Connectors installer](../../images/selecting_the_connectors_installer.png) +![Selecting the Connectors installer](../images/selecting_the_connectors_installer.png) Selecting the Connectors installer From 4395389405e7c279aa18b25db1b9525126f59c6d Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 12:23:26 -0400 Subject: [PATCH 12/32] Changes to deploy.mjs for OCL --- install_template/deploy.mjs | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 94fae7fc2be..6f300c87310 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -293,27 +293,27 @@ const moveDoc = async (product, platform, version) => { (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_20.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_sles_12.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles15_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_sles_15.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_deb10_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_deb_10.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_deb11_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_deb_11.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_ubuntu_18.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_ubuntu_20.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_centos7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_centos_7.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_other_linux8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_other_linux_8.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_8.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_7.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_centos7_${fmtArchFilename(ctx)}.mdx`), From d0318cc1a19e4214baadb1cdf2e50eb297c771de Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 12:28:01 -0400 Subject: [PATCH 13/32] changed install landing pages to include "and derivatives"; also added Windows for JDBC --- .../docs/jdbc_connector/42.5.0.1/installing/index.mdx | 11 ++++++----- .../docs/ocl_connector/14.1.0.1/installing/index.mdx | 10 +++++----- 2 files changed, 11 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index 2764fe169c5..fe9339e5b85 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -22,19 +22,20 @@ legacyRedirectsGenerated: ## [Linux x86-64 (amd64)](linux_x86_64) -### Red Hat Enterprise Linux (RHEL) family +### Red Hat Enterprise Linux (RHEL) and derivatives - [RHEL 8](linux_x86_64/jdbc_rhel_8), [RHEL 7](linux_x86_64/jdbc_rhel_7) - [Oracle Linux (OL) 8](linux_x86_64/jdbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/jdbc_rhel_7) - [Rocky Linux 8](linux_x86_64/jdbc_other_linux_8) - [AlmaLinux 8](linux_x86_64/jdbc_other_linux_8) - [CentOS 7](linux_x86_64/jdbc_centos_7) -### SUSE Linux Enterprise (SLES) family +### SUSE Linux Enterprise (SLES) and derivatives - [SLES 15](linux_x86_64/jdbc_sles_15), [SLES 12](linux_x86_64/jdbc_sles_12) -### Debian family +### Debian and derivatives - [Ubuntu 20.04](linux_x86_64/jdbc_ubuntu_20), [Ubuntu 18.04](linux_x86_64/jdbc_ubuntu_18) - [Debian 11](linux_x86_64/jdbc_deb_11), [Debian 10](linux_x86_64/jdbc_deb_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) -### Red Hat Enterprise Linux (RHEL) family +### Red Hat Enterprise Linux (RHEL) and derivatives - [RHEL 8](linux_ppc64le/jdbc_rhel_8) -### SUSE Linux Enterprise (SLES) family +### SUSE Linux Enterprise (SLES) and derivatives - [SLES 15](linux_ppc64le/jdbc_sles_15), [SLES 12](linux_ppc64le/jdbc_sles_12) +## [Windows](windows) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx index 287231bada6..6e07e070503 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -10,20 +10,20 @@ navigation: --- ## [Linux x86-64 (amd64)](linux_x86_64) -### Red Hat Enterprise Linux (RHEL) family +### Red Hat Enterprise Linux (RHEL) and derivatives - [RHEL 8](linux_x86_64/ocl_connector_rhel_8), [RHEL 7](linux_x86_64/ocl_connector_rhel_7) - [Oracle Linux (OL) 8](linux_x86_64/ocl_connector_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_connector_rhel_7) - [Rocky Linux 8](linux_x86_64/ocl_connector_other_linux_8) - [AlmaLinux 8](linux_x86_64/ocl_connector_other_linux_8) - [CentOS 7](linux_x86_64/ocl_connector_centos_7) -### SUSE Linux Enterprise (SLES) family +### SUSE Linux Enterprise (SLES) and derivatives - [SLES 15](linux_x86_64/ocl_connector_sles_15), [SLES 12](linux_x86_64/ocl_connector_sles_12) -### Debian family +### Debian and derivatives - [Ubuntu 20.04](linux_x86_64/ocl_connector_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_connector_ubuntu_18) - [Debian 11](linux_x86_64/ocl_connector_deb_11), [Debian 10](linux_x86_64/ocl_connector_deb_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) -### Red Hat Enterprise Linux (RHEL) family +### Red Hat Enterprise Linux (RHEL) and derivatives - [RHEL 8](linux_ppc64le/ocl_connector_rhel_8) -### SUSE Linux Enterprise (SLES) family +### SUSE Linux Enterprise (SLES) and derivatives - [SLES 15](linux_ppc64le/ocl_connector_sles_15), [SLES 12](linux_ppc64le/ocl_connector_sles_12) ## [Windows](windows) \ No newline at end of file From 2f72933c0cbeba5661139f175af05727db7a7876 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 26 Oct 2022 12:34:53 -0400 Subject: [PATCH 14/32] modified derivatives language to be consistent --- .../docs/jdbc_connector/42.5.0.1/installing/index.mdx | 4 ++-- product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index fe9339e5b85..d113a65998a 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -34,8 +34,8 @@ legacyRedirectsGenerated: - [Ubuntu 20.04](linux_x86_64/jdbc_ubuntu_20), [Ubuntu 18.04](linux_x86_64/jdbc_ubuntu_18) - [Debian 11](linux_x86_64/jdbc_deb_11), [Debian 10](linux_x86_64/jdbc_deb_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) -### Red Hat Enterprise Linux (RHEL) and derivatives +### Red Hat Enterprise Linux (RHEL) - [RHEL 8](linux_ppc64le/jdbc_rhel_8) -### SUSE Linux Enterprise (SLES) and derivatives +### SUSE Linux Enterprise (SLES) - [SLES 15](linux_ppc64le/jdbc_sles_15), [SLES 12](linux_ppc64le/jdbc_sles_12) ## [Windows](windows) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx index 6e07e070503..4a1ab320f8a 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -22,8 +22,8 @@ navigation: - [Ubuntu 20.04](linux_x86_64/ocl_connector_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_connector_ubuntu_18) - [Debian 11](linux_x86_64/ocl_connector_deb_11), [Debian 10](linux_x86_64/ocl_connector_deb_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) -### Red Hat Enterprise Linux (RHEL) and derivatives +### Red Hat Enterprise Linux (RHEL) - [RHEL 8](linux_ppc64le/ocl_connector_rhel_8) -### SUSE Linux Enterprise (SLES) and derivatives +### SUSE Linux Enterprise (SLES) - [SLES 15](linux_ppc64le/ocl_connector_sles_15), [SLES 12](linux_ppc64le/ocl_connector_sles_12) ## [Windows](windows) \ No newline at end of file From a9028b90b4565bfa293b70f22bd88d69ff2dcbd6 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Fri, 28 Oct 2022 09:10:23 -0400 Subject: [PATCH 15/32] changed deb to debian for JDBC and OCL --- install_template/deploy.mjs | 8 ++++---- .../docs/jdbc_connector/42.5.0.1/installing/index.mdx | 2 +- .../42.5.0.1/installing/linux_x86_64/index.mdx | 8 ++++---- .../linux_x86_64/{jdbc_deb_10.mdx => jdbc_debian_10.mdx} | 0 .../linux_x86_64/{jdbc_deb_11.mdx => jdbc_debian_11.mdx} | 0 .../docs/ocl_connector/14.1.0.1/installing/index.mdx | 2 +- .../14.1.0.1/installing/linux_x86_64/index.mdx | 9 ++++----- ..._connector_deb_10.mdx => ocl_connector_debian_10.mdx} | 0 ..._connector_deb_11.mdx => ocl_connector_debian_11.mdx} | 0 9 files changed, 14 insertions(+), 15 deletions(-) rename product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/{jdbc_deb_10.mdx => jdbc_debian_10.mdx} (100%) rename product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/{jdbc_deb_11.mdx => jdbc_debian_11.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_deb_10.mdx => ocl_connector_debian_10.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_deb_11.mdx => ocl_connector_debian_11.mdx} (100%) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 6f300c87310..23137659518 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -284,9 +284,9 @@ const moveDoc = async (product, platform, version) => { when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 15"}}, (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_sles_15.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_deb_10.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_debian_10.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_deb_11.mdx`), + (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_debian_11.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 18.04"}}, (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_18.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, @@ -297,9 +297,9 @@ const moveDoc = async (product, platform, version) => { when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_sles_15.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_deb_10.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_debian_10.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_deb_11.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_debian_11.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 18.04"}}, (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_ubuntu_18.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 20.04"}}, diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index d113a65998a..7c8b1564b37 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -32,7 +32,7 @@ legacyRedirectsGenerated: - [SLES 15](linux_x86_64/jdbc_sles_15), [SLES 12](linux_x86_64/jdbc_sles_12) ### Debian and derivatives - [Ubuntu 20.04](linux_x86_64/jdbc_ubuntu_20), [Ubuntu 18.04](linux_x86_64/jdbc_ubuntu_18) -- [Debian 11](linux_x86_64/jdbc_deb_11), [Debian 10](linux_x86_64/jdbc_deb_10) +- [Debian 11](linux_x86_64/jdbc_debian_11), [Debian 10](linux_x86_64/jdbc_debian_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) ### Red Hat Enterprise Linux (RHEL) - [RHEL 8](linux_ppc64le/jdbc_rhel_8) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx index 4018429a010..e9ac85c314d 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx @@ -13,8 +13,8 @@ navigation: - jdbc_ubuntu_22 - jdbc_ubuntu_20 - jdbc_ubuntu_18 -- jdbc_deb_11 -- jdbc_deb_10 +- jdbc_debian_11 +- jdbc_debian_10 --- For operating system-specific install instructions, see: @@ -28,6 +28,6 @@ For operating system-specific install instructions, see: - [SLES 12](jdbc_sles_12) - [Ubuntu 20.04](jdbc_ubuntu_20) - [Ubuntu 18.04](jdbc_ubuntu_18) - - [Debian 11](jdbc_deb_11) - - [Debian 10](jdbc_deb_10) + - [Debian 11](jdbc_debian_11) + - [Debian 10](jdbc_debian_10) diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_10.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_deb_11.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx index 4a1ab320f8a..379d441a6f6 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -20,7 +20,7 @@ navigation: - [SLES 15](linux_x86_64/ocl_connector_sles_15), [SLES 12](linux_x86_64/ocl_connector_sles_12) ### Debian and derivatives - [Ubuntu 20.04](linux_x86_64/ocl_connector_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_connector_ubuntu_18) -- [Debian 11](linux_x86_64/ocl_connector_deb_11), [Debian 10](linux_x86_64/ocl_connector_deb_10) +- [Debian 11](linux_x86_64/ocl_connector_debian_11), [Debian 10](linux_x86_64/ocl_connector_debian_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) ### Red Hat Enterprise Linux (RHEL) - [RHEL 8](linux_ppc64le/ocl_connector_rhel_8) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx index 4d5c6e7c4ca..2cc14775bfe 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx @@ -13,12 +13,11 @@ navigation: - ocl_connector_ubuntu_22 - ocl_connector_ubuntu_20 - ocl_connector_ubuntu_18 -- ocl_connector_deb_11 -- ocl_connector_deb_10 +- ocl_connector_debian_11 +- ocl_connector_debian_10 --- For operating system-specific install instructions, see: - - [RHEL 8/OL 8](ocl_connector_rhel_8) @@ -29,7 +28,7 @@ For operating system-specific install instructions, see: - [SLES 12](ocl_connector_sles_12) - [Ubuntu 20.04](ocl_connector_ubuntu_20) - [Ubuntu 18.04](ocl_connector_ubuntu_18) - - [Debian 11](ocl_connector_deb_11) - - [Debian 10](ocl_connector_deb_10) + - [Debian 11](ocl_connector_debian_11) + - [Debian 10](ocl_connector_debian_10) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_10.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_10.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_10.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_10.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_11.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_11.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_deb_11.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_11.mdx From 1f2b2545714356bf60ba1cca095dcadaa8c6c420 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Fri, 28 Oct 2022 09:58:06 -0400 Subject: [PATCH 16/32] all changes for ODBC except deploy.mjs --- .../ibm_power_ppc64le/index.mdx | 16 --------- .../01_installing_linux/index.mdx | 36 ------------------- .../01_installing_linux/x86_amd64/index.mdx | 32 ----------------- .../13/03_installing_edb_odbc/index.mdx | 13 ------- product_docs/docs/odbc_connector/13/index.mdx | 7 ++-- .../odbc_connector/13/installing/index.mdx | 31 ++++++++++++++++ .../13/installing/linux_ppc64le/index.mdx | 18 ++++++++++ .../linux_ppc64le/odbc_rhel_8.mdx} | 0 .../linux_ppc64le/odbc_sles_12.mdx} | 0 .../linux_ppc64le/odbc_sles_15.mdx} | 0 .../13/installing/linux_x86_64/index.mdx | 32 +++++++++++++++++ .../linux_x86_64/odbc_centos_7.mdx} | 0 .../linux_x86_64/odbc_debian_10.mdx} | 0 .../linux_x86_64/odbc_debian_11.mdx} | 0 .../linux_x86_64/odbc_other_linux_8.mdx} | 0 .../linux_x86_64/odbc_rhel_7.mdx} | 0 .../linux_x86_64/odbc_rhel_8.mdx} | 0 .../linux_x86_64/odbc_sles_12.mdx} | 0 .../linux_x86_64/odbc_sles_15.mdx} | 0 .../linux_x86_64/odbc_ubuntu_18.mdx} | 0 .../linux_x86_64/odbc_ubuntu_20.mdx} | 0 .../upgrading.mdx} | 2 ++ .../windows.mdx} | 5 +-- 23 files changed, 91 insertions(+), 101 deletions(-) delete mode 100644 product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx delete mode 100644 product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/index.mdx delete mode 100644 product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/index.mdx delete mode 100644 product_docs/docs/odbc_connector/13/03_installing_edb_odbc/index.mdx create mode 100644 product_docs/docs/odbc_connector/13/installing/index.mdx create mode 100644 product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx => installing/linux_ppc64le/odbc_rhel_8.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx => installing/linux_ppc64le/odbc_sles_12.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx => installing/linux_ppc64le/odbc_sles_15.mdx} (100%) create mode 100644 product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx => installing/linux_x86_64/odbc_centos_7.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx => installing/linux_x86_64/odbc_debian_10.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx => installing/linux_x86_64/odbc_debian_11.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx => installing/linux_x86_64/odbc_other_linux_8.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx => installing/linux_x86_64/odbc_rhel_7.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx => installing/linux_x86_64/odbc_rhel_8.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx => installing/linux_x86_64/odbc_sles_12.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx => installing/linux_x86_64/odbc_sles_15.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx => installing/linux_x86_64/odbc_ubuntu_18.mdx} (100%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx => installing/linux_x86_64/odbc_ubuntu_20.mdx} (100%) rename product_docs/docs/odbc_connector/13/{13_upgrading_rpm_install.mdx => installing/upgrading.mdx} (92%) rename product_docs/docs/odbc_connector/13/{03_installing_edb_odbc/14_installing_windows.mdx => installing/windows.mdx} (95%) diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx deleted file mode 100644 index c068927e330..00000000000 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/index.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Installing EDB ODBC Connector on IBM Power (ppc64le)" -navTitle: "IBM Power (ppc64le)" -navigation: -- odbc13_rhel8_ppcle -- odbc13_sles15_ppcle -- odbc13_sles12_ppcle ---- - -For operating system-specific install instructions, see: - - - [RHEL 8](odbc13_rhel8_ppcle) - - - [SLES 15](odbc13_sles15_ppcle) - - [SLES 12](odbc13_sles12_ppcle) - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/index.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/index.mdx deleted file mode 100644 index 7f263acfaa4..00000000000 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/index.mdx +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: "Installing on Linux" -navTitle: Linux -navigation: -- x86_amd64 -- ibm_power_ppc64le ---- - -To install the EDB ODBC Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). - -For platform-specific install instructions, see: - -- Linux x86-64 (amd64): - - [RHEL 8/OL 8](x86_amd64/odbc13_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](x86_amd64/odbc13_other_linux8_x86) - - [RHEL 7/OL 7](x86_amd64/odbc13_rhel7_x86) - - [CentOS 7](x86_amd64/odbc13_centos7_x86) - - [SLES 15](x86_amd64/odbc13_sles15_x86) - - [SLES 12](x86_amd64/odbc13_sles12_x86) - - [Ubuntu 20.04](x86_amd64/odbc13_ubuntu20_x86) - - [Ubuntu 18.04](x86_amd64/odbc13_ubuntu18_x86) - - [Debian 11](x86_amd64/odbc13_deb11_x86) - - [Debian 10](x86_amd64/odbc13_deb10_x86) - -- Linux on IBM Power (ppc64le): - - [RHEL 8](ibm_power_ppc64le/odbc13_rhel8_ppcle) - - - [SLES 12](ibm_power_ppc64le/odbc13_sles12_ppcle) - - [SLES 15](ibm_power_ppc64le/odbc13_sles15_ppcle) - - - - - - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/index.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/index.mdx deleted file mode 100644 index 8e62fb47fdb..00000000000 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/index.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Installing EDB ODBC Connector on Linux x86 (amd64)" -navTitle: "Intel x86 (amd64)" -navigation: -- odbc13_rhel8_x86 -- odbc13_other_linux8_x86 -- odbc13_rhel7_x86 -- odbc13_centos7_x86 -- odbc13_sles15_x86 -- odbc13_sles12_x86 -- odbc13_ubuntu22_x86 -- odbc13_ubuntu20_x86 -- odbc13_ubuntu18_x86 -- odbc13_deb11_x86 -- odbc13_deb10_x86 ---- - -For operating system-specific install instructions, see: - - - [RHEL 8/OL 8](odbc13_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](odbc13_other_linux8_x86) - - [RHEL 7/OL 7](odbc13_rhel7_x86) - - [CentOS 7](odbc13_centos7_x86) - - [SLES 15](odbc13_sles15_x86) - - [SLES 12](odbc13_sles12_x86) - - [Ubuntu 20.04](odbc13_ubuntu20_x86) - - [Ubuntu 18.04](odbc13_ubuntu18_x86) - - [Debian 11](odbc13_deb11_x86) - - [Debian 10](odbc13_deb10_x86) - - diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/index.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/index.mdx deleted file mode 100644 index d2f94429cd3..00000000000 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/index.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "Installing the EDB ODBC Connector" -redirects: - - ../03_edb-odbc_overview/01_installing_edb-odbc ---- - -You can install the EDB ODBC Connector on: - -- [Linux](01_installing_linux) -- [Windows](14_installing_windows) - - - diff --git a/product_docs/docs/odbc_connector/13/index.mdx b/product_docs/docs/odbc_connector/13/index.mdx index 210a6b9f4ba..532a1bbe899 100644 --- a/product_docs/docs/odbc_connector/13/index.mdx +++ b/product_docs/docs/odbc_connector/13/index.mdx @@ -7,8 +7,11 @@ redirects: navigation: - 01_odbc_rel_notes - 02_requirements_overview - - 03_installing_edb_odbc - - 13_upgrading_rpm_install + - installing + - 04_creating_a_data_source + - 05_edb-odbc_connection_properties + - 06_edb-odbc_driver_functionality + - 07_scram_compatibility --- ODBC (Open Database Connectivity) is a programming interface that allows a client application to connect to any database that provides an ODBC driver. EDB ODBC Connector is an interface that allows an ODBC-compliant client application to connect to an EDB Postgres Advanced Server database. The EDB ODBC Connector allows an application that was designed to work with other databases to run on EDB Postgres Advanced Server. The ODBC Connector provides a way for the client application to establish a connection, send queries, and retrieve results from EDB Postgres Advanced Server. diff --git a/product_docs/docs/odbc_connector/13/installing/index.mdx b/product_docs/docs/odbc_connector/13/installing/index.mdx new file mode 100644 index 00000000000..5ab9ba05cdf --- /dev/null +++ b/product_docs/docs/odbc_connector/13/installing/index.mdx @@ -0,0 +1,31 @@ +--- +title: "Installing the EDB ODBC Connector" +navTitle: "Installing" +redirects: + - ../03_edb-odbc_overview/01_installing_edb-odbc + - /odbc/13/03_installing_edb_odbc +navigation: + - linux_x86_64 + - linux_ppc64le + - windows + - upgrading +--- + +## [Linux x86-64 (amd64)](linux_x86_64) +### Red Hat Enterprise Linux (RHEL) and derivatives +- [RHEL 8](linux_x86_64/odbc_rhel_8), [RHEL 7](linux_x86_64/odbc_rhel_7) +- [Oracle Linux (OL) 8](linux_x86_64/odbc_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/odbc_rhel_7) +- [Rocky Linux 8](linux_x86_64/odbc_other_linux_8) +- [AlmaLinux 8](linux_x86_64/odbc_other_linux_8) +- [CentOS 7](linux_x86_64/odbc_centos_7) +### SUSE Linux Enterprise (SLES) and derivatives +- [SLES 15](linux_x86_64/odbc_sles_15), [SLES 12](linux_x86_64/odbc_sles_12) +### Debian and derivatives +- [Ubuntu 20.04](linux_x86_64/odbc_ubuntu_20), [Ubuntu 18.04](linux_x86_64/odbc_ubuntu_18) +- [Debian 11](linux_x86_64/odbc_debian_11), [Debian 10](linux_x86_64/odbc_debian_10) +## [Linux on IBM Power (ppc64le)](linux_ppc64le) +### Red Hat Enterprise Linux (RHEL) +- [RHEL 8](linux_ppc64le/odbc_rhel_8) +### SUSE Linux Enterprise (SLES) +- [SLES 15](linux_ppc64le/odbc_sles_15), [SLES 12](linux_ppc64le/odbc_sles_12) +## [Windows](windows) \ No newline at end of file diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx new file mode 100644 index 00000000000..565cd5fa684 --- /dev/null +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/index.mdx @@ -0,0 +1,18 @@ +--- +title: "Installing EDB ODBC Connector on IBM Power (ppc64le)" +navTitle: "On Linux ppc64le" +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/ +navigation: +- odbc_rhel_8 +- odbc_sles_15 +- odbc_sles_12 +--- + +For operating system-specific install instructions, see: + + - [RHEL 8](odbc_rhel_8) + + - [SLES 15](odbc_sles_15) + - [SLES 12](odbc_sles_12) + diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx new file mode 100644 index 00000000000..a668b4c6b37 --- /dev/null +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/index.mdx @@ -0,0 +1,32 @@ +--- +title: "Installing EDB ODBC Connector on Linux x86 (amd64)" +navTitle: "On Linux x86" +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/ +navigation: +- odbc_rhel_8 +- odbc_other_linux_8 +- odbc_rhel_7 +- odbc_centos_7 +- odbc_sles_15 +- odbc_sles_12 +- odbc_ubuntu_22 +- odbc_ubuntu_20 +- odbc_ubuntu_18 +- odbc_debian_11 +- odbc_debian_10 +--- + +For operating system-specific install instructions, see: + + - [RHEL 8/OL 8](odbc_rhel_8) + + - [Rocky Linux 8/AlmaLinux 8](odbc_other_linux_8) + - [RHEL 7/OL 7](odbc_rhel_7) + - [CentOS 7](odbc_centos_7) + - [SLES 15](odbc_sles_15) + - [SLES 12](odbc_sles_12) + - [Ubuntu 20.04](odbc_ubuntu_20) + - [Ubuntu 18.04](odbc_ubuntu_18) + - [Debian 11](odbc_debian_11) + - [Debian 10](odbc_debian_10) diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx similarity index 100% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx rename to product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx diff --git a/product_docs/docs/odbc_connector/13/13_upgrading_rpm_install.mdx b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx similarity index 92% rename from product_docs/docs/odbc_connector/13/13_upgrading_rpm_install.mdx rename to product_docs/docs/odbc_connector/13/installing/upgrading.mdx index bed010027e7..63d71107ac4 100644 --- a/product_docs/docs/odbc_connector/13/13_upgrading_rpm_install.mdx +++ b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx @@ -1,7 +1,9 @@ --- title: Upgrading a Linux installation +navTitle: "Upgrading" redirects: - 03_edb-odbc_overview/13_upgrading_rpm_install + - /odbc_connector/13/13_upgrading_rpm_install.mdx --- If you have an existing EDB ODBC connector RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/14_installing_windows.mdx b/product_docs/docs/odbc_connector/13/installing/windows.mdx similarity index 95% rename from product_docs/docs/odbc_connector/13/03_installing_edb_odbc/14_installing_windows.mdx rename to product_docs/docs/odbc_connector/13/installing/windows.mdx index 5847b1a0698..6c43caa5315 100644 --- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/14_installing_windows.mdx +++ b/product_docs/docs/odbc_connector/13/installing/windows.mdx @@ -1,7 +1,8 @@ --- title: "Installing the ODBC Connector on Windows" -navTitle: Windows - +navTitle: On Windows +redirects: + - /odbc_connector/13/03_installing_edb_odbc/14_installing_windows/ --- You can use the EDB Connectors Installation wizard to add the ODBC connector to your system; the wizard is available at the [EDB website](https://www.enterprisedb.com/software-downloads-postgres/). From d98a51e9d23344a6f4ebf901aa3efcade094b586 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Fri, 28 Oct 2022 10:07:30 -0400 Subject: [PATCH 17/32] updates to deploy.mjjs for ODBC --- install_template/deploy.mjs | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 23137659518..110d0ebbac4 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -316,27 +316,27 @@ const moveDoc = async (product, platform, version) => { (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_centos7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_centos_7.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_other_linux8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_other_linux_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel7_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_7.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_rhel8_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_sles12_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_sles_12.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_sles15_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_sles_15.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_deb10_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_debian_10.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_deb11_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_debian_11.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_ubuntu_18.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `odbc_connector/13/03_installing_edb_odbc/01_installing_linux/${fmtArchPath(ctx)}/odbc13_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_ubuntu_20.mdx`), when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "Debian 11"}}, (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_deb11_${fmtArchFilename(ctx)}.mdx`), From 2f52c62ace041821f6560afc6677c5d5a20cc51c Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Fri, 28 Oct 2022 10:16:45 -0400 Subject: [PATCH 18/32] changed file names from ocl_connector to ocl along with all associated changes --- install_template/deploy.mjs | 22 +++++----- .../14.1.0.1/installing/index.mdx | 20 ++++----- .../installing/linux_ppc64le/index.mdx | 12 +++--- ...cl_connector_rhel_8.mdx => ocl_rhel_8.mdx} | 0 ..._connector_sles_12.mdx => ocl_sles_12.mdx} | 0 ..._connector_sles_15.mdx => ocl_sles_15.mdx} | 0 .../installing/linux_x86_64/index.mdx | 42 +++++++++---------- ...onnector_centos_7.mdx => ocl_centos_7.mdx} | 0 ...nector_debian_10.mdx => ocl_debian_10.mdx} | 0 ...nector_debian_11.mdx => ocl_debian_11.mdx} | 0 ...ther_linux_8.mdx => ocl_other_linux_8.mdx} | 0 ...cl_connector_rhel_7.mdx => ocl_rhel_7.mdx} | 0 ...cl_connector_rhel_8.mdx => ocl_rhel_8.mdx} | 0 ..._connector_sles_12.mdx => ocl_sles_12.mdx} | 0 ..._connector_sles_15.mdx => ocl_sles_15.mdx} | 0 ...nector_ubuntu_18.mdx => ocl_ubuntu_18.mdx} | 0 ...nector_ubuntu_20.mdx => ocl_ubuntu_20.mdx} | 0 17 files changed, 48 insertions(+), 48 deletions(-) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/{ocl_connector_rhel_8.mdx => ocl_rhel_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/{ocl_connector_sles_12.mdx => ocl_sles_12.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/{ocl_connector_sles_15.mdx => ocl_sles_15.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_centos_7.mdx => ocl_centos_7.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_debian_10.mdx => ocl_debian_10.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_debian_11.mdx => ocl_debian_11.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_other_linux_8.mdx => ocl_other_linux_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_rhel_7.mdx => ocl_rhel_7.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_rhel_8.mdx => ocl_rhel_8.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_sles_12.mdx => ocl_sles_12.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_sles_15.mdx => ocl_sles_15.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_ubuntu_18.mdx => ocl_ubuntu_18.mdx} (100%) rename product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/{ocl_connector_ubuntu_20.mdx => ocl_ubuntu_20.mdx} (100%) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 110d0ebbac4..9311f2d439e 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -293,27 +293,27 @@ const moveDoc = async (product, platform, version) => { (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_20.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_sles_12.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_sles_12.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_sles_15.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_sles_15.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_debian_10.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_debian_10.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_debian_11.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_debian_11.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_ubuntu_18.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_ubuntu_18.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_ubuntu_20.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_ubuntu_20.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_centos_7.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_centos_7.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_other_linux_8.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_other_linux_8.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_8.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_8.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_7.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_7.mdx`), when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_connector_rhel_8.mdx`), + (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_8.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_centos_7.mdx`), diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx index 379d441a6f6..551e7d525bb 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -11,19 +11,19 @@ navigation: ## [Linux x86-64 (amd64)](linux_x86_64) ### Red Hat Enterprise Linux (RHEL) and derivatives -- [RHEL 8](linux_x86_64/ocl_connector_rhel_8), [RHEL 7](linux_x86_64/ocl_connector_rhel_7) -- [Oracle Linux (OL) 8](linux_x86_64/ocl_connector_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_connector_rhel_7) -- [Rocky Linux 8](linux_x86_64/ocl_connector_other_linux_8) -- [AlmaLinux 8](linux_x86_64/ocl_connector_other_linux_8) -- [CentOS 7](linux_x86_64/ocl_connector_centos_7) +- [RHEL 8](linux_x86_64/ocl_rhel_8), [RHEL 7](linux_x86_64/ocl_rhel_7) +- [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/ocl_rhel_7) +- [Rocky Linux 8](linux_x86_64/ocl_other_linux_8) +- [AlmaLinux 8](linux_x86_64/ocl_other_linux_8) +- [CentOS 7](linux_x86_64/ocl_centos_7) ### SUSE Linux Enterprise (SLES) and derivatives -- [SLES 15](linux_x86_64/ocl_connector_sles_15), [SLES 12](linux_x86_64/ocl_connector_sles_12) +- [SLES 15](linux_x86_64/ocl_sles_15), [SLES 12](linux_x86_64/ocl_sles_12) ### Debian and derivatives -- [Ubuntu 20.04](linux_x86_64/ocl_connector_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_connector_ubuntu_18) -- [Debian 11](linux_x86_64/ocl_connector_debian_11), [Debian 10](linux_x86_64/ocl_connector_debian_10) +- [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20), [Ubuntu 18.04](linux_x86_64/ocl_ubuntu_18) +- [Debian 11](linux_x86_64/ocl_debian_11), [Debian 10](linux_x86_64/ocl_debian_10) ## [Linux on IBM Power (ppc64le)](linux_ppc64le) ### Red Hat Enterprise Linux (RHEL) -- [RHEL 8](linux_ppc64le/ocl_connector_rhel_8) +- [RHEL 8](linux_ppc64le/ocl_rhel_8) ### SUSE Linux Enterprise (SLES) -- [SLES 15](linux_ppc64le/ocl_connector_sles_15), [SLES 12](linux_ppc64le/ocl_connector_sles_12) +- [SLES 15](linux_ppc64le/ocl_sles_15), [SLES 12](linux_ppc64le/ocl_sles_12) ## [Windows](windows) \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx index affec384909..3fcc23b2bb5 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx @@ -4,14 +4,14 @@ navTitle: "On Linux ppc64le" redirects: - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le navigation: -- ocl_connector_rhel_8 -- ocl_connector_sles_15 -- ocl_connector_sles_12 +- ocl_rhel_8 +- ocl_sles_15 +- ocl_sles_12 --- For operating system-specific install instructions, see: - - [RHEL 8](ocl_connector_rhel_8) + - [RHEL 8](ocl_rhel_8) - - [SLES 15](ocl_connector_sles_15) - - [SLES 12](ocl_connector_sles_12) + - [SLES 15](ocl_sles_15) + - [SLES 12](ocl_sles_12) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_rhel_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_rhel_8.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_12.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_12.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_15.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_connector_sles_15.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx index 2cc14775bfe..febc8c77a61 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx @@ -4,31 +4,31 @@ navTitle: "On Linux x86" redirects: - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64 navigation: -- ocl_connector_rhel_8 -- ocl_connector_other_linux_8 -- ocl_connector_rhel_7 -- ocl_connector_centos_7 -- ocl_connector_sles_15 -- ocl_connector_sles_12 -- ocl_connector_ubuntu_22 -- ocl_connector_ubuntu_20 -- ocl_connector_ubuntu_18 -- ocl_connector_debian_11 -- ocl_connector_debian_10 +- ocl_rhel_8 +- ocl_other_linux_8 +- ocl_rhel_7 +- ocl_centos_7 +- ocl_sles_15 +- ocl_sles_12 +- ocl_ubuntu_22 +- ocl_ubuntu_20 +- ocl_ubuntu_18 +- ocl_debian_11 +- ocl_debian_10 --- For operating system-specific install instructions, see: - - [RHEL 8/OL 8](ocl_connector_rhel_8) + - [RHEL 8/OL 8](ocl_rhel_8) - - [Rocky Linux 8/AlmaLinux 8](ocl_connector_other_linux_8) - - [RHEL 7/OL 8](ocl_connector_rhel_7) - - [RHEL CentOS 7](ocl_connector_centos_7) - - [SLES 15](ocl_connector_sles_15) - - [SLES 12](ocl_connector_sles_12) - - [Ubuntu 20.04](ocl_connector_ubuntu_20) - - [Ubuntu 18.04](ocl_connector_ubuntu_18) - - [Debian 11](ocl_connector_debian_11) - - [Debian 10](ocl_connector_debian_10) + - [Rocky Linux 8/AlmaLinux 8](ocl_other_linux_8) + - [RHEL 7/OL 8](ocl_rhel_7) + - [RHEL CentOS 7](ocl_centos_7) + - [SLES 15](ocl_sles_15) + - [SLES 12](ocl_sles_12) + - [Ubuntu 20.04](ocl_ubuntu_20) + - [Ubuntu 18.04](ocl_ubuntu_18) + - [Debian 11](ocl_debian_11) + - [Debian 10](ocl_debian_10) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_centos_7.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_centos_7.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_10.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_10.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_11.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_debian_11.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_other_linux_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_other_linux_8.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_7.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_7.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_rhel_8.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_12.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_12.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_15.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_sles_15.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_18.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_18.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_20.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx similarity index 100% rename from product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_connector_ubuntu_20.mdx rename to product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx From 42da7dcf56b247ac7ab60e9a76c1c7841bf7f6fb Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 7 Nov 2022 12:02:47 -0500 Subject: [PATCH 19/32] first set of modifications based on Josh's new system of redirects --- .../templates/products/edb-jdbc-connector/base.njk | 14 ++++++++++++++ .../products/edb-jdbc-connector/ubuntu-22.04.njk | 6 +++++- .../templates/products/edb-ocl-connector/base.njk | 13 +++++++++++++ .../products/edb-ocl-connector/ubuntu-22.04.njk | 6 +++++- .../templates/products/edb-odbc-connector/base.njk | 13 +++++++++++++ .../products/edb-odbc-connector/ubuntu-22.04.njk | 6 +++++- 6 files changed, 55 insertions(+), 3 deletions(-) diff --git a/install_template/templates/products/edb-jdbc-connector/base.njk b/install_template/templates/products/edb-jdbc-connector/base.njk index ac0b0ac4ffa..b7ad3404de0 100644 --- a/install_template/templates/products/edb-jdbc-connector/base.njk +++ b/install_template/templates/products/edb-jdbc-connector/base.njk @@ -1,5 +1,19 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-jdbc{% endset %} + +{% import "platformBase/_deploymentConstants.njk" as deploy %} +{% block frontmatter %} +{# + If you modify deployment path here, please first copy the old expression + and add it to the list under "redirects:" below - this ensures we don't + break any existing links. +#} +deployPath: edb-jdbc-connector/{{ product.version }}/installing/linux_{{platform.arch}}/jdbc_{{deploy.map_platform[platform.name]}}.mdx +redirects: + - edb-jdbc-connector/{{ product.version }}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{{deploy.expand_arch[platform.arch]}}/jdbc_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx +{% endblock frontmatter %} + + {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} - Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. diff --git a/install_template/templates/products/edb-jdbc-connector/ubuntu-22.04.njk b/install_template/templates/products/edb-jdbc-connector/ubuntu-22.04.njk index c66a0eb637d..820879d2702 100644 --- a/install_template/templates/products/edb-jdbc-connector/ubuntu-22.04.njk +++ b/install_template/templates/products/edb-jdbc-connector/ubuntu-22.04.njk @@ -1,2 +1,6 @@ {% extends "products/edb-jdbc-connector/base.njk" %} -{% set platformBaseTemplate = "ubuntu-22.04" %} \ No newline at end of file +{% set platformBaseTemplate = "ubuntu-22.04" %} +{% set osFilenamePart="ubuntu_22" %} +{% block frontmatter %} +{# remove this block when Ubuntu 22 is released #} +{% endblock frontmatter %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/base.njk b/install_template/templates/products/edb-ocl-connector/base.njk index 36fc7ce47d7..d38fb66d431 100644 --- a/install_template/templates/products/edb-ocl-connector/base.njk +++ b/install_template/templates/products/edb-ocl-connector/base.njk @@ -1,5 +1,18 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-oci{% endset %} + +{% import "platformBase/_deploymentConstants.njk" as deploy %} +{% block frontmatter %} +{# + If you modify deployment path here, please first copy the old expression + and add it to the list under "redirects:" below - this ensures we don't + break any existing links. +#} +deployPath: edb-ocl-connector/{{ product.version }}/installing/linux_{{platform.arch}}/ocl_{{deploy.map_platform[platform.name]}}.mdx +redirects: + - edb-ocl-connector/{{ product.version }}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx +{% endblock frontmatter %} + {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} {% endblock prodprereq %} diff --git a/install_template/templates/products/edb-ocl-connector/ubuntu-22.04.njk b/install_template/templates/products/edb-ocl-connector/ubuntu-22.04.njk index a536696d419..d1e82c5c4a8 100644 --- a/install_template/templates/products/edb-ocl-connector/ubuntu-22.04.njk +++ b/install_template/templates/products/edb-ocl-connector/ubuntu-22.04.njk @@ -1,2 +1,6 @@ {% extends "products/edb-ocl-connector/ubuntu.njk" %} -{% set platformBaseTemplate = "ubuntu-22.04" %} \ No newline at end of file +{% set platformBaseTemplate = "ubuntu-22.04" %} +{% set osFilenamePart="ubuntu_22" %} +{% block frontmatter %} +{# remove this block when Ubuntu 22 is released #} +{% endblock frontmatter %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/base.njk b/install_template/templates/products/edb-odbc-connector/base.njk index 5c20e6d236f..859f4aa3f6f 100644 --- a/install_template/templates/products/edb-odbc-connector/base.njk +++ b/install_template/templates/products/edb-odbc-connector/base.njk @@ -1,5 +1,18 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-odbc{% endset %} + +{% import "platformBase/_deploymentConstants.njk" as deploy %} +{% block frontmatter %} +{# + If you modify deployment path here, please first copy the old expression + and add it to the list under "redirects:" below - this ensures we don't + break any existing links. +#} +deployPath: mongo_data_adapter/{{ product.version }}/installing/linux_{{platform.arch}}/mongo_{{deploy.map_platform[platform.name]}}.mdx +redirects: + - odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx +{% endblock frontmatter %} + {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} {% endblock prodprereq %} diff --git a/install_template/templates/products/edb-odbc-connector/ubuntu-22.04.njk b/install_template/templates/products/edb-odbc-connector/ubuntu-22.04.njk index 21e164f924b..2d7473cca71 100644 --- a/install_template/templates/products/edb-odbc-connector/ubuntu-22.04.njk +++ b/install_template/templates/products/edb-odbc-connector/ubuntu-22.04.njk @@ -1,2 +1,6 @@ {% extends "products/edb-odbc-connector/ubuntu.njk" %} -{% set platformBaseTemplate = "ubuntu-22.04" %} \ No newline at end of file +{% set platformBaseTemplate = "ubuntu-22.04" %} +{% set osFilenamePart="ubuntu_22" %} +{% block frontmatter %} +{# remove this block when Ubuntu 22 is released #} +{% endblock frontmatter %} \ No newline at end of file From cea002db55b43c2de22176f07a55ade9f3b4088b Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 8 Nov 2022 11:26:04 -0500 Subject: [PATCH 20/32] updates to templates for connectors including redirects for JDBC --- install_template/config.yaml | 56 +++++++++---------- .../products/edb-jdbc-connector/base.njk | 4 +- .../products/edb-ocl-connector/base.njk | 4 +- .../products/edb-odbc-connector/base.njk | 4 +- .../42.5.0.1/installing/index.mdx | 4 -- .../installing/linux_ppc64le/index.mdx | 2 - .../installing/linux_ppc64le/jdbc_rhel_8.mdx | 4 +- .../installing/linux_ppc64le/jdbc_sles_12.mdx | 4 +- .../installing/linux_ppc64le/jdbc_sles_15.mdx | 4 +- .../installing/linux_x86_64/index.mdx | 2 - .../installing/linux_x86_64/jdbc_centos_7.mdx | 4 +- .../linux_x86_64/jdbc_debian_10.mdx | 4 +- .../linux_x86_64/jdbc_debian_11.mdx | 4 +- .../linux_x86_64/jdbc_other_linux_8.mdx | 4 +- .../installing/linux_x86_64/jdbc_rhel_7.mdx | 4 +- .../installing/linux_x86_64/jdbc_rhel_8.mdx | 4 +- .../installing/linux_x86_64/jdbc_sles_12.mdx | 4 +- .../installing/linux_x86_64/jdbc_sles_15.mdx | 4 +- .../linux_x86_64/jdbc_ubuntu_18.mdx | 4 +- .../linux_x86_64/jdbc_ubuntu_20.mdx | 4 +- .../installing/linux_ppc64le/ocl_rhel_8.mdx | 4 +- .../installing/linux_ppc64le/ocl_sles_12.mdx | 4 +- .../installing/linux_ppc64le/ocl_sles_15.mdx | 4 +- .../installing/linux_x86_64/ocl_centos_7.mdx | 4 +- .../installing/linux_x86_64/ocl_debian_10.mdx | 4 +- .../installing/linux_x86_64/ocl_debian_11.mdx | 4 +- .../linux_x86_64/ocl_other_linux_8.mdx | 4 +- .../installing/linux_x86_64/ocl_rhel_7.mdx | 4 +- .../installing/linux_x86_64/ocl_rhel_8.mdx | 4 +- .../installing/linux_x86_64/ocl_sles_12.mdx | 4 +- .../installing/linux_x86_64/ocl_sles_15.mdx | 4 +- .../installing/linux_x86_64/ocl_ubuntu_18.mdx | 4 +- .../installing/linux_x86_64/ocl_ubuntu_20.mdx | 4 +- .../installing/linux_ppc64le/odbc_rhel_8.mdx | 4 +- .../installing/linux_ppc64le/odbc_sles_12.mdx | 4 +- .../installing/linux_ppc64le/odbc_sles_15.mdx | 4 +- .../installing/linux_x86_64/odbc_centos_7.mdx | 4 +- .../linux_x86_64/odbc_debian_10.mdx | 4 +- .../linux_x86_64/odbc_debian_11.mdx | 4 +- .../linux_x86_64/odbc_other_linux_8.mdx | 4 +- .../installing/linux_x86_64/odbc_rhel_7.mdx | 4 +- .../installing/linux_x86_64/odbc_rhel_8.mdx | 4 +- .../installing/linux_x86_64/odbc_sles_12.mdx | 4 +- .../installing/linux_x86_64/odbc_sles_15.mdx | 4 +- .../linux_x86_64/odbc_ubuntu_18.mdx | 4 +- .../linux_x86_64/odbc_ubuntu_20.mdx | 4 +- 46 files changed, 151 insertions(+), 81 deletions(-) diff --git a/install_template/config.yaml b/install_template/config.yaml index d957fdb126c..db683946978 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -3,46 +3,46 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: RHEL 8 arch: ppc64le - supported versions: [42] + supported versions: [42.5.0.1] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: Debian 10 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: Debian 11 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: SLES 12 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: SLES 12 arch: ppc64le - supported versions: [42] + supported versions: [42.5.0.1] - name: SLES 15 arch: x86_64 - supported versions: [42] + supported versions: [42.5.0.1] - name: SLES 15 arch: ppc64le - supported versions: [42] + supported versions: [42.5.0.1] - name: Migration Toolkit platforms: - name: RHEL 8 or OL 8 @@ -135,46 +135,46 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: RHEL 8 arch: ppc64le - supported versions: [13.1.0.2] + supported versions: [13] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: Debian 10 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: Debian 11 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: SLES 12 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: SLES 12 arch: ppc64le - supported versions: [13.1.0.2] + supported versions: [13] - name: SLES 15 arch: x86_64 - supported versions: [13.1.0.2] + supported versions: [13] - name: SLES 15 arch: ppc64le - supported versions: [13.1.0.2] + supported versions: [13] - name: EDB pgBouncer platforms: - name: CentOS 7 diff --git a/install_template/templates/products/edb-jdbc-connector/base.njk b/install_template/templates/products/edb-jdbc-connector/base.njk index b7ad3404de0..ae3efc81f46 100644 --- a/install_template/templates/products/edb-jdbc-connector/base.njk +++ b/install_template/templates/products/edb-jdbc-connector/base.njk @@ -8,9 +8,9 @@ and add it to the list under "redirects:" below - this ensures we don't break any existing links. #} -deployPath: edb-jdbc-connector/{{ product.version }}/installing/linux_{{platform.arch}}/jdbc_{{deploy.map_platform[platform.name]}}.mdx +deployPath: jdbc_connector/{{ product.version }}/installing/linux_{{platform.arch}}/jdbc_{{deploy.map_platform[platform.name]}}.mdx redirects: - - edb-jdbc-connector/{{ product.version }}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{{deploy.expand_arch[platform.arch]}}/jdbc_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - jdbc_connector/{{ product.version }}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{{deploy.expand_arch[platform.arch]}}/jdbc42_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx {% endblock frontmatter %} diff --git a/install_template/templates/products/edb-ocl-connector/base.njk b/install_template/templates/products/edb-ocl-connector/base.njk index d38fb66d431..11de039068e 100644 --- a/install_template/templates/products/edb-ocl-connector/base.njk +++ b/install_template/templates/products/edb-ocl-connector/base.njk @@ -8,9 +8,9 @@ and add it to the list under "redirects:" below - this ensures we don't break any existing links. #} -deployPath: edb-ocl-connector/{{ product.version }}/installing/linux_{{platform.arch}}/ocl_{{deploy.map_platform[platform.name]}}.mdx +deployPath: ocl_connector/{{ product.version }}/installing/linux_{{platform.arch}}/ocl_{{deploy.map_platform[platform.name]}}.mdx redirects: - - edb-ocl-connector/{{ product.version }}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - ocl_connector/{{ product.version }}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx {% endblock frontmatter %} {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} diff --git a/install_template/templates/products/edb-odbc-connector/base.njk b/install_template/templates/products/edb-odbc-connector/base.njk index 859f4aa3f6f..6481db520d9 100644 --- a/install_template/templates/products/edb-odbc-connector/base.njk +++ b/install_template/templates/products/edb-odbc-connector/base.njk @@ -8,9 +8,9 @@ and add it to the list under "redirects:" below - this ensures we don't break any existing links. #} -deployPath: mongo_data_adapter/{{ product.version }}/installing/linux_{{platform.arch}}/mongo_{{deploy.map_platform[platform.name]}}.mdx +deployPath: odbc_connector/{{ product.version }}/installing/linux_{{platform.arch}}/odbc_{{deploy.map_platform[platform.name]}}.mdx redirects: - - odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/{{deploy.expand_arch[platform.arch]}}/odbc_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx {% endblock frontmatter %} {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index 7c8b1564b37..94f83b02bd7 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -1,10 +1,6 @@ --- title: "Installing and configuring EDB JDBC Connector" navTitle: "Installing" -redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package - navigation: - linux_x86_64 - linux_ppc64le diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx index 3a9547b1580..b0f41264809 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx @@ -1,8 +1,6 @@ --- title: "Installing EDB JDBC Connector on IBM Power (ppc64le)" navTitle: "On Linux ppc64le" -redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le navigation: - jdbc_rhel_8 - jdbc_sles_15 diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx index e0b03d4085d..0456de45f17 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 title: Installing EDB JDBC Connector on RHEL 8 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx index 084b973f6e4..c344ebaf0ed 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB JDBC Connector on SLES 12 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx index 4358009b71e..395ca5ebd3c 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB JDBC Connector on SLES 15 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx index e9ac85c314d..2ef9a6f175c 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx @@ -1,8 +1,6 @@ --- title: "Installing EDB JDBC Connector on Linux x86 (amd64)" navTitle: "On Linux x86" -redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64 navigation: - jdbc_rhel_8 - jdbc_other_linux_8 diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx index 1c1cbabdf5e..98d75808987 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_centos_7.mdx @@ -1,10 +1,12 @@ --- navTitle: CentOS 7 title: Installing EDB JDBC Connector on CentOS 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx index 6445b75c35f..1728119a3e2 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_10.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 10 title: Installing EDB JDBC Connector on Debian 10 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx index 513c2aeeccd..f5d45ef2149 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_debian_11.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 11 title: Installing EDB JDBC Connector on Debian 11 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx index 59ec01bcae1..6e0e41762e8 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_other_linux_8.mdx @@ -1,10 +1,12 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing EDB JDBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx index 57b5f91efe7..ea8432fe9bf 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_7.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 7 or OL 7 title: Installing EDB JDBC Connector on RHEL 7 or OL 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx index c1abcb02423..de4b50f65e2 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 or OL 8 title: Installing EDB JDBC Connector on RHEL 8 or OL 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx index 59df87fbb1b..5eb5b8a1e12 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB JDBC Connector on SLES 12 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx index 4ead1a556ee..797cd689624 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB JDBC Connector on SLES 15 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx index e637847950b..a4fb99a8611 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_18.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB JDBC Connector on Ubuntu 18.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx index 4b435c83e7b..29f2d2ab811 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB JDBC Connector on Ubuntu 20.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx index 0b90dc0ae36..7aef7a64883 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 title: Installing EDB OCL Connector on RHEL 8 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_rhel8_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx index 72b5e45232c..fac2b871674 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB OCL Connector on SLES 12 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles12_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx index 600b7b73682..3370f607bec 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB OCL Connector on SLES 15 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles15_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx index d9748745979..f458c2652c9 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_centos_7.mdx @@ -1,10 +1,12 @@ --- navTitle: CentOS 7 title: Installing EDB OCL Connector on CentOS 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx index 8ca057c4f8a..6409da9a6f0 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_10.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 10 title: Installing EDB OCL Connector on Debian 10 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx index a970d52943d..b2bbcb4c975 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_debian_11.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 11 title: Installing EDB OCL Connector on Debian 11 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx index c6c9b862e77..abc3d4b0fc8 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -1,10 +1,12 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx index 54bf2fcf957..c66256a0d89 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_7.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 7 or OL 7 title: Installing EDB OCL Connector on RHEL 7 or OL 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx index ba3a093615f..9e60c03eed9 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 or OL 8 title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx index c968a86c9eb..63446c7abd1 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB OCL Connector on SLES 12 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx index 877951acbdb..6bc0a69e28c 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB OCL Connector on SLES 15 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx index 00987ce6bbe..30bb815ca38 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_18.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB OCL Connector on Ubuntu 18.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx index 6f75af125a7..f01ec1a1399 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/mongo_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx index 38607af2b13..d9d14ba900d 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 title: Installing EDB ODBC Connector on RHEL 8 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_rhel8_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx index 6a454dd094e..4998e7b23ab 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB ODBC Connector on SLES 12 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_sles12_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx index 5901688c113..86077bafc12 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB ODBC Connector on SLES 15 ppc64le - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_sles15_ppc64le --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx index 83546e0890f..3aa15f320fd 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx @@ -1,10 +1,12 @@ --- navTitle: CentOS 7 title: Installing EDB ODBC Connector on CentOS 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx index de37424463a..285b1516bdf 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 10 title: Installing EDB ODBC Connector on Debian 10 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx index a3b23f78e6d..2010d27b77e 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx @@ -1,10 +1,12 @@ --- navTitle: Debian 11 title: Installing EDB ODBC Connector on Debian 11 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx index 5cbb70bf9d4..0d0f404690e 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx @@ -1,10 +1,12 @@ --- navTitle: AlmaLinux 8 or Rocky Linux 8 title: Installing EDB ODBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx index 51130a402f1..9f4217ab304 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 7 or OL 7 title: Installing EDB ODBC Connector on RHEL 7 or OL 7 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx index 0c026562026..92f4cc5baaf 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx @@ -1,10 +1,12 @@ --- navTitle: RHEL 8 or OL 8 title: Installing EDB ODBC Connector on RHEL 8 or OL 8 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx index 7746e42b59a..31d7c889d95 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 12 title: Installing EDB ODBC Connector on SLES 12 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx index 4e890738668..41009d8f6ec 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx @@ -1,10 +1,12 @@ --- navTitle: SLES 15 title: Installing EDB ODBC Connector on SLES 15 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx index f167ff3efb1..7406c764f95 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 18.04 title: Installing EDB ODBC Connector on Ubuntu 18.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx index a9cf9da705f..d0e7d94e3db 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx @@ -1,10 +1,12 @@ --- navTitle: Ubuntu 20.04 title: Installing EDB ODBC Connector on Ubuntu 20.04 x86_64 - # This topic is generated from templates. If you have feedback on it, instead of # editing the page and creating a pull request, please enter a GitHub issue and # the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_ubuntu20_x86 --- ## Prerequisites From c99922942e92ecdea1e2fa8e9269ed358893b592 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 15 Nov 2022 13:12:17 -0500 Subject: [PATCH 21/32] final changes including redirects for jdbc --- install_template/deploy.mjs | 67 +++++++++++++------ .../products/edb-jdbc-connector/base.njk | 2 +- .../42.5.0.1/installing/index.mdx | 3 + .../installing/linux_ppc64le/index.mdx | 2 + .../installing/linux_ppc64le/jdbc_rhel_8.mdx | 2 +- .../installing/linux_ppc64le/jdbc_sles_12.mdx | 2 +- .../installing/linux_ppc64le/jdbc_sles_15.mdx | 2 +- .../installing/linux_x86_64/index.mdx | 2 + .../42.5.0.1/installing/windows.mdx | 1 + 9 files changed, 57 insertions(+), 26 deletions(-) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 9311f2d439e..e2bca3636ba 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -292,28 +292,51 @@ const moveDoc = async (product, platform, version) => { when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_20.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_sles_12.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_sles_15.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_debian_10.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_debian_11.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_ubuntu_18.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_ubuntu_20.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_centos_7.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_other_linux_8.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_8.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_7.mdx`), - when({product: {name: "EDB OCL Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `ocl_connector/${ctx.product.version}/installing/linux_${ctx.platform.arch}/ocl_rhel_8.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "CentOS 7"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel_8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 12"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 15"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 11"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb11_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 10"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 18.04"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 20.04"}}, + (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + + when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 12"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles12_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 15"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles15_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 10"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 11"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb11_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 18.04"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu18_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 20.04"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "CentOS 7"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8"}}, + (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_centos_7.mdx`), diff --git a/install_template/templates/products/edb-jdbc-connector/base.njk b/install_template/templates/products/edb-jdbc-connector/base.njk index ae3efc81f46..4f1863eab6b 100644 --- a/install_template/templates/products/edb-jdbc-connector/base.njk +++ b/install_template/templates/products/edb-jdbc-connector/base.njk @@ -10,7 +10,7 @@ #} deployPath: jdbc_connector/{{ product.version }}/installing/linux_{{platform.arch}}/jdbc_{{deploy.map_platform[platform.name]}}.mdx redirects: - - jdbc_connector/{{ product.version }}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{{deploy.expand_arch[platform.arch]}}/jdbc42_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - jdbc_connector/{{ product.version }}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{{deploy.expand_arch[platform.arch]}}/jdbc42_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx {% endblock frontmatter %} diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx index 94f83b02bd7..9efb0b875d5 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/index.mdx @@ -7,6 +7,9 @@ navigation: - windows - configuring_for_java - upgrading +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/ + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/installing_and_configuring_the_jdbc_connector.html" diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx index b0f41264809..759878a656c 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/index.mdx @@ -1,6 +1,8 @@ --- title: "Installing EDB JDBC Connector on IBM Power (ppc64le)" navTitle: "On Linux ppc64le" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/ navigation: - jdbc_rhel_8 - jdbc_sles_15 diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx index 0456de45f17..357e80cbae6 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB JDBC Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppc64le + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx index c344ebaf0ed..13a13499007 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB JDBC Connector on SLES 12 ppc64le # the documentation team will update the templates accordingly. redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppc64le + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx index 395ca5ebd3c..c5b83430759 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_ppc64le/jdbc_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB JDBC Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppc64le + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx index 2ef9a6f175c..476930257d9 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/linux_x86_64/index.mdx @@ -1,6 +1,8 @@ --- title: "Installing EDB JDBC Connector on Linux x86 (amd64)" navTitle: "On Linux x86" +redirects: + - /jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/ navigation: - jdbc_rhel_8 - jdbc_other_linux_8 diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx index b7d3fb7d112..717df966fb1 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/installing/windows.mdx @@ -53,6 +53,7 @@ When StackBuilder Plus opens, follow the onscreen instructions. Select the `Ente ![Selecting the Connectors installer](../images/selecting_the_connectors_installer.png) + Selecting the Connectors installer Follow the directions of the onscreen wizard to add/update an installation of the EDB Connectors. From bf25e249927361a976ab08eb38413afa23b953ca Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 15 Nov 2022 13:34:19 -0500 Subject: [PATCH 22/32] Final changes for OCL --- install_template/templates/products/edb-ocl-connector/base.njk | 2 +- product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx | 3 ++- .../ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx | 2 +- .../ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx | 2 +- .../docs/ocl_connector/14.1.0.1/installing/upgrading.mdx | 2 +- .../docs/ocl_connector/14.1.0.1/installing/windows.mdx | 2 +- 6 files changed, 7 insertions(+), 6 deletions(-) diff --git a/install_template/templates/products/edb-ocl-connector/base.njk b/install_template/templates/products/edb-ocl-connector/base.njk index 11de039068e..73f9d0ab368 100644 --- a/install_template/templates/products/edb-ocl-connector/base.njk +++ b/install_template/templates/products/edb-ocl-connector/base.njk @@ -10,7 +10,7 @@ #} deployPath: ocl_connector/{{ product.version }}/installing/linux_{{platform.arch}}/ocl_{{deploy.map_platform[platform.name]}}.mdx redirects: - - ocl_connector/{{ product.version }}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - ocl_connector/{{ product.version }}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/{{deploy.expand_arch[platform.arch]}}/mongo_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx {% endblock frontmatter %} {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx index 551e7d525bb..5ad98cb20d7 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/index.mdx @@ -1,7 +1,8 @@ --- title: "Installing" redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ navigation: - linux_x86_64 - linux_ppc64le diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx index 3fcc23b2bb5..d690ac31f4c 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/index.mdx @@ -2,7 +2,7 @@ title: "Installing EDB OCL Connector on IBM Power (ppc64le)" navTitle: "On Linux ppc64le" redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ navigation: - ocl_rhel_8 - ocl_sles_15 diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx index febc8c77a61..865cca43b17 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_x86_64/index.mdx @@ -2,7 +2,7 @@ title: "Installing EDB OCL Connector on Linux x86 (amd64)" navTitle: "On Linux x86" redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64 + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ navigation: - ocl_rhel_8 - ocl_other_linux_8 diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx index f5aedc40a38..3bbf0a2d5dc 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/upgrading.mdx @@ -2,7 +2,7 @@ title: "Upgrading a Linux installation" navTitle: "Upgrading" redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install/ --- If you have an existing `OCL Connector` RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx index 5dbf6567dd8..e64002e4068 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/windows.mdx @@ -2,7 +2,7 @@ title: "Installing on Windows" navTitle: "On Windows" redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows/ --- From 627bd8d126c172d19f625e613c8e2c376be5c63e Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 15 Nov 2022 15:28:38 -0500 Subject: [PATCH 23/32] final changes for ODBC including redirects --- .../templates/products/edb-odbc-connector/base.njk | 2 +- .../14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx | 2 +- .../14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx | 2 +- .../14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx | 2 +- product_docs/docs/odbc_connector/13/installing/index.mdx | 3 ++- .../odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx | 2 +- .../13/installing/linux_ppc64le/odbc_sles_12.mdx | 2 +- .../13/installing/linux_ppc64le/odbc_sles_15.mdx | 2 +- .../13/installing/linux_x86_64/odbc_centos_7.mdx | 2 +- .../13/installing/linux_x86_64/odbc_debian_10.mdx | 2 +- .../13/installing/linux_x86_64/odbc_debian_11.mdx | 2 +- .../13/installing/linux_x86_64/odbc_other_linux_8.mdx | 2 +- .../odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx | 2 +- .../odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx | 2 +- .../odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx | 2 +- .../odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx | 2 +- .../13/installing/linux_x86_64/odbc_ubuntu_18.mdx | 2 +- .../13/installing/linux_x86_64/odbc_ubuntu_20.mdx | 2 +- product_docs/docs/odbc_connector/13/installing/upgrading.mdx | 2 +- 19 files changed, 20 insertions(+), 19 deletions(-) diff --git a/install_template/templates/products/edb-odbc-connector/base.njk b/install_template/templates/products/edb-odbc-connector/base.njk index 6481db520d9..bac48db1aa3 100644 --- a/install_template/templates/products/edb-odbc-connector/base.njk +++ b/install_template/templates/products/edb-odbc-connector/base.njk @@ -10,7 +10,7 @@ #} deployPath: odbc_connector/{{ product.version }}/installing/linux_{{platform.arch}}/odbc_{{deploy.map_platform[platform.name]}}.mdx redirects: - - odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/{{deploy.expand_arch[platform.arch]}}/odbc_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace("_64", "")}}.mdx + - odbc_connector/{{ product.version }}/03_installing_edb_odbc/01_installing_linux/{{deploy.expand_arch[platform.arch]}}/odbc13_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx {% endblock frontmatter %} {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %} diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx index 7aef7a64883..3fca2f668e5 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_rhel8_ppc64le + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx index fac2b871674..fdab067b218 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 12 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles12_ppc64le + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles12_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx index 3370f607bec..43502eb6082 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/installing/linux_ppc64le/ocl_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles15_ppc64le + - /ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/mongo_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/index.mdx b/product_docs/docs/odbc_connector/13/installing/index.mdx index 5ab9ba05cdf..5035681f474 100644 --- a/product_docs/docs/odbc_connector/13/installing/index.mdx +++ b/product_docs/docs/odbc_connector/13/installing/index.mdx @@ -3,7 +3,8 @@ title: "Installing the EDB ODBC Connector" navTitle: "Installing" redirects: - ../03_edb-odbc_overview/01_installing_edb-odbc - - /odbc/13/03_installing_edb_odbc + - /odbc_connector/13/03_installing_edb_odbc/ + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ navigation: - linux_x86_64 - linux_ppc64le diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx index d9d14ba900d..7f22fe53338 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_rhel8_ppc64le + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx index 4998e7b23ab..341cb174d5b 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 12 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_sles12_ppc64le + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx index 86077bafc12..3559aee0ecd 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_ppc64le/odbc_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc_sles15_ppc64le + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx index 3aa15f320fd..83cffa0834e 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_centos_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on CentOS 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_centos7_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx index 285b1516bdf..891c06828fd 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_10.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Debian 10 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_deb10_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx index 2010d27b77e..80de863ae2a 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_debian_11.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Debian 11 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_deb11_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx index 0d0f404690e..ad4b503963a 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_other_linux_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_other_linux8_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx index 9f4217ab304..b85e940a8ef 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 7 or OL 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_rhel7_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx index 92f4cc5baaf..281d3c7d9a2 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 8 or OL 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_rhel8_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx index 31d7c889d95..796bd395123 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 12 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_sles12_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx index 41009d8f6ec..a06a0089276 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 15 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_sles15_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx index 7406c764f95..2e7d4fd1f1d 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_18.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Ubuntu 18.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_ubuntu18_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx index d0e7d94e3db..2fbdaa94069 100644 --- a/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx +++ b/product_docs/docs/odbc_connector/13/installing/linux_x86_64/odbc_ubuntu_20.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Ubuntu 20.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc_ubuntu20_x86 + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/13/installing/upgrading.mdx b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx index 63d71107ac4..c91c0eac56e 100644 --- a/product_docs/docs/odbc_connector/13/installing/upgrading.mdx +++ b/product_docs/docs/odbc_connector/13/installing/upgrading.mdx @@ -3,7 +3,7 @@ title: Upgrading a Linux installation navTitle: "Upgrading" redirects: - 03_edb-odbc_overview/13_upgrading_rpm_install - - /odbc_connector/13/13_upgrading_rpm_install.mdx + - /odbc_connector/13/13_upgrading_rpm_install --- If you have an existing EDB ODBC connector RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: From 59396fd596df147f806f1fd18f14d087ce172557 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 17 Nov 2022 10:30:10 -0500 Subject: [PATCH 24/32] removing EFM and MTK lines from deploy --- install_template/deploy.mjs | 96 +------------------------------------ 1 file changed, 1 insertion(+), 95 deletions(-) diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index e2bca3636ba..0ddb288984d 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -269,101 +269,7 @@ const moveDoc = async (product, platform, version) => { when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Ubuntu 18.04"}}, (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_centos_7.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_other_linux_8.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_7.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_8.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_rhel_8.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_sles_12.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_sles_15.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_debian_10.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_debian_11.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_18.mdx`), - when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `jdbc_connector/42.5.0.1/installing/linux_${ctx.platform.arch}/jdbc_ubuntu_20.mdx`), - - when({product: {name: "Failover Manager", version: 4}, platform: {name: "CentOS 7"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_centos7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_other_linux8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel_8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 12"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 15"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 11"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb11_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 10"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb10_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu18_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - - when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 12"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles12_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 15"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles15_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 10"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb10_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 11"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb11_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu18_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu20_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_other_linux8_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "CentOS 7"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_centos7_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8"}}, - (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`), - - when({product: {name: "EDB ODBC Connector"}, platform: {name: "CentOS 7"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_centos_7.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_other_linux_8.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8 or OL 8"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_8.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 7 or OL 7"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_7.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "RHEL 8"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_rhel_8.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 12"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_sles_12.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "SLES 15"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_sles_15.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "Debian 10"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_debian_10.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "Debian 11"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_debian_11.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "Ubuntu 18.04"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_ubuntu_18.mdx`), - when({product: {name: "EDB ODBC Connector"}, platform: {name: "Ubuntu 20.04"}}, - (ctx) => `odbc_connector/13/installing/linux_${ctx.platform.arch}/odbc_ubuntu_20.mdx`), - - when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "Debian 11"}}, - (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_deb11_${fmtArchFilename(ctx)}.mdx`), - when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "RHEL 8 or OL 8"}}, + when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "RHEL 8 or OL 8"}}, (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB pgBouncer", version: 1.17}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, (ctx) => `pgbouncer/1.17/01_installation/install_on_linux/${fmtArchPath(ctx)}/pgbouncer_other_linux8_${fmtArchFilename(ctx)}.mdx`), From 352e4af1296642dac9d024f4e96bc8734a3d0134 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 17 Nov 2022 11:41:49 -0500 Subject: [PATCH 25/32] more edtis to spl programs section --- .../02_spl_block_structure.mdx | 25 +++++++++---------- .../02_spl_programs/03_anonymous_blocks.mdx | 6 ++--- 2 files changed, 15 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx index 2b65791734e..1e7b39d64ef 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx @@ -8,11 +8,11 @@ legacyRedirectsGenerated: -Regardless of whether the program is a procedure, function, subprogram, or trigger, an SPL program has the same *block* structure. A block consists of up to three sections - an optional declaration section, a mandatory executable section, and an optional exception section. Minimally, a block has an executable section that consists of one or more SPL statements within the keywords, `BEGIN` and `END`. +Regardless of whether the program is a procedure, function, subprogram, or trigger, an SPL program has the same *block* structure. A block consists of up to three sections: an optional declaration section, a mandatory executable section, and an optional exception section. Minimally, a block has an executable section that consists of one or more SPL statements between the keywords `BEGIN` and `END`. -The optional declaration section is used to declare variables, cursors, types, and subprograms that are used by the statements within the executable and exception sections. Declarations appear just prior to the `BEGIN` keyword of the executable section. Depending upon the context of where the block is used, the declaration section may begin with the keyword `DECLARE`. +Use the optional declaration section to declare variables, cursors, types, and subprograms that are used by the statements in the executable and exception sections. Declarations appear just before the `BEGIN` keyword of the executable section. Depending on the context of where the block is used, the declaration section can begin with the keyword `DECLARE`. -You can include an exception section within the `BEGIN - END` block. The exception section begins with the keyword, `EXCEPTION`, and continues until the end of the block in which it appears. If an exception is thrown by a statement within the block, program control goes to the exception section where the thrown exception may or may not be handled depending upon the exception and the contents of the exception section. +You can include an exception section in the `BEGIN - END` block. The exception section begins with the keyword `EXCEPTION` and continues until the end of the block in which it appears. If an exception is thrown by a statement in the block, program control might go to the exception section where the thrown exception is handled, depending on the exception and the contents of the exception section. The following is the general structure of a block: @@ -28,16 +28,15 @@ The following is the general structure of a block: END; ``` -`pragmas` are the directives (`AUTONOMOUS_TRANSACTION` is the currently supported pragma). `declarations` are one or more variable, cursor, type, or subprogram declarations that are local to the block. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations. Each declaration must be terminated by a semicolon. The use of the keyword `DECLARE` depends upon the context in which the block appears. - -`statements` are one or more SPL statements. Each statement must be terminated by a semicolon. The end of the block denoted by the keyword `END` must also be terminated by a semicolon. - -If present, the keyword `EXCEPTION` marks the beginning of the exception section. `exception_condition` is a conditional expression testing for one or more types of exceptions. If an exception matches one of the exceptions in `exception_condition`, the `statements` following the `WHEN exception_condition` clause are executed. There may be one or more `WHEN exception_condition` clauses, each followed by `statements`. +- `pragmas` are the directives (`AUTONOMOUS_TRANSACTION` is the currently supported pragma). +- `declarations` are one or more variable, cursor, type, or subprogram declarations that are local to the block. If subprogram declarations are included, you must declare them after all other variable, cursor, and type declarations. Terminate each declaration with a semicolon. The use of the keyword `DECLARE` depends on the context in which the block appears. +- `statements` are one or more SPL statements. Terminate each statement with a semicolon. You must also terminate the end of the block denoted by the keyword `END` with a semicolon. +- If present, the keyword `EXCEPTION` marks the beginning of the exception section. `exception_condition` is a conditional expression testing for one or more types of exceptions. If an exception matches one of the exceptions in `exception_condition`, the `statements` following the `WHEN exception_condition` clause are executed. There can be one or more `WHEN exception_condition` clauses, each followed by `statements`. !!! Note - A `BEGIN/END` block in itself, is considered a statement; thus, blocks may be nested. The exception section may also contain nested blocks. + A `BEGIN/END` block is considered a statement, thus you can nest blocks. The exception section can also contain nested blocks. -The following is the simplest possible block consisting of the `NULL` statement within the executable section. The `NULL` statement is an executable statement that does nothing. +The following is the simplest possible block, consisting of the `NULL` statement in the executable section. The `NULL` statement is an executable statement that does nothing. ```text BEGIN @@ -45,7 +44,7 @@ BEGIN END; ``` -The following block contains a declaration section as well as the executable section. +The following block contains a declaration section as well as the executable section: ```text DECLARE @@ -61,7 +60,7 @@ BEGIN END; ``` -In this example, three numeric variables are declared of data type `NUMBER`. Values are assigned to two of the variables, and one number is divided by the other, storing the results in a third variable which is then displayed. If executed, the output would be: +In this example, three numeric variables are declared of data type `NUMBER`. Values are assigned to two of the variables, and one number is divided by the other. Results are stored in a third variable and then displayed. The output is: ```text 75 divided by 14 is 5.36 @@ -86,7 +85,7 @@ EXCEPTION END; ``` -The following output shows that the statement within the exception section is executed as a result of the division by zero. +The following output shows that the statement in the exception section is executed as a result of the division by zero: ```text An exception occurred diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx index e73290c9766..5a5e2e768c1 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx @@ -8,8 +8,8 @@ legacyRedirectsGenerated: -Blocks are typically written as part of a procedure, function, subprogram, or trigger. Procedure, function, and trigger programs are named and stored in the database for re-use. For quick (one-time) execution (such as testing), you can simply enter the block without providing a name or storing it in the database. +You typically write blocks as part of a procedure, function, subprogram, or trigger. You name procedure, function, and trigger programs and store them in the database if you want to reuse them. -A block of this type is called an *anonymous block*. An anonymous block is unnamed and is not stored in the database. Once the block has been executed and erased from the application buffer, it cannot be re-executed unless the block code is re-entered into the application. +For quick, one-time execution such as testing, you can enter the block without providing a name or storing it in the database. A block without a name and that isn't stored in the database is called an *anonymous block*. Once the block is executed and erased from the application buffer, you can't execute it again unless the block code you enter it into the application again. -Typically, the same block of code executes many times. To run a block of code repeatedly without reentering the code each time, with some simple modifications, an anonymous block can be turned into a procedure or function. The following sections discuss how to create a procedure or function that can be stored in the database and invoked repeatedly by another procedure, function, or application program. +Typically, the same block of code executes many times. To run a block of code repeatedly without reentering the code each time, with some simple modifications, you can turn an anonymous block into a procedure or function. See [Procedures overview](04_procedures_overview) and [Functions overview](05_functions_overview). From 9d2f8f6801c1dc3da2f9ad31522f33f62c8c18f3 Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Thu, 20 Oct 2022 19:44:09 +0530 Subject: [PATCH 26/32] Update cli.mdx --- product_docs/docs/biganimal/release/reference/cli.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/reference/cli.mdx b/product_docs/docs/biganimal/release/reference/cli.mdx index 5d0c8ca28c1..37e07183351 100644 --- a/product_docs/docs/biganimal/release/reference/cli.mdx +++ b/product_docs/docs/biganimal/release/reference/cli.mdx @@ -229,6 +229,8 @@ Here is a sample configuration file in YAML format with Azure specified as the p instanceType: azure:Standard_D4s_v4 # volumeType: azurepremiumstorage # volumeProperties: P1 # + volumePropertySize: "4Gi" # + volumePropertyIOPS: 3000 # : Applicable to AWS gp3 and Azure Ultradisk, volume Input/Output Operations Per Second> networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -238,6 +240,7 @@ Here is a sample configuration file in YAML format with Azure specified as the p pgConfigMap: # application_name: test_app # array_nulls: true # + backupRetentionPeriod: 30d # --- ``` @@ -321,6 +324,7 @@ After the cluster is created, you can update attributes of the cluster including - Networking - Allowed IP list - Postgres database configuration +- Retention period For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: @@ -381,7 +385,8 @@ biganimal restore-cluster \ --volume-property "P1" \ --networking "public" \ --cidr-blocks="10.10.10.10/27=Traffic from App B" \ - --restore-point "2022-01-26T15:04:05+0800" + --restore-point "2022-01-26T15:04:05+0800" \ + --backup-retention-period 3m ``` The password for the restored cluster is a mandatory. The other parameters, if not specified, inherit the source database's settings. In interactive mode, the source database's settings appear as the default input, or appear as the first option in a selection list. From c227e60bcdb5db28bd2ed1f88bdfd9513f6734e2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 17 Nov 2022 12:02:04 -0500 Subject: [PATCH 27/32] fixed typos --- product_docs/docs/biganimal/release/reference/cli.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli.mdx b/product_docs/docs/biganimal/release/reference/cli.mdx index 37e07183351..be1584845d6 100644 --- a/product_docs/docs/biganimal/release/reference/cli.mdx +++ b/product_docs/docs/biganimal/release/reference/cli.mdx @@ -106,7 +106,7 @@ biganimal config set context_credential ba-user1 ## Configuring The initial running of the CLI creates a hidden configuration folder in your user root directory. For example, for Linux it’s `${HOME}/.edb-cli`. The CLI persists the configuration file in this directory as well as the credentials. -Don’t edit files in this directory directly. Instead, use the `config` subcommand to list and update the configuration settings of the CLI. Use the following command to get detailed usage and available configurations inforamtion: +Don’t edit files in this directory directly. Instead, use the `config` subcommand to list and update the configuration settings of the CLI. Use the following command to get detailed usage and available configurations information: ```shell biganimal config ``` @@ -308,7 +308,7 @@ biganimal show-cluster-connection \ --name my-biganimal-cluster \ --provider azure \ --region eastus \ - --ouput json + --output json ``` !!! From 8a71e52f47a92dc3c39d72558b8d8c67c1e19e09 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 17 Nov 2022 16:31:11 -0500 Subject: [PATCH 28/32] two more sections of SPL text --- ...ion_errors_in_procedures_and_functions.mdx | 14 +++---- .../epas_compat_spl/02_spl_programs/index.mdx | 4 +- .../01_declaring_a_variable.mdx | 8 ++-- ...2_using__type_in_variable_declarations.mdx | 30 ++++++++------- ...using__row_type_in_record_declarations.mdx | 9 +++-- ...ined_record_types_and_record_variables.mdx | 37 +++++++------------ .../03_variable_declarations/index.mdx | 2 +- .../04_basic_statements/01_assignment.mdx | 6 +-- .../04_basic_statements/02_delete.mdx | 10 ++--- .../04_basic_statements/03_insert.mdx | 12 +++--- .../04_basic_statements/04_null.mdx | 6 +-- .../05_using_the_returning_into_clause.mdx | 24 +++++++----- .../04_basic_statements/06_select_into.mdx | 27 +++++++------- .../04_basic_statements/07_update.mdx | 10 ++--- .../08_obtaining_the_result_status.mdx | 8 ++-- .../04_basic_statements/index.mdx | 2 +- 16 files changed, 104 insertions(+), 105 deletions(-) diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx index 7f250315505..f29eb826431 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx @@ -8,9 +8,9 @@ legacyRedirectsGenerated: -When the EDB Postgres Advanced Server parsers compile a procedure or function, they confirm that both the `CREATE` statement and the program body (that portion of the program that follows the `AS` keyword) conforms to the grammar rules for SPL and SQL constructs. By default, the server terminates the compilation process if a parser detects an error. Note that the parsers detect syntax errors in expressions, but not semantic errors (i.e. an expression referencing a non-existent column, table, or function, or a value of incorrect type). +When the EDB Postgres Advanced Server parsers compile a procedure or function, they confirm that both the `CREATE` statement and the program body (the portion of the program that follows the `AS` keyword) conform to the grammar rules for SPL and SQL constructs. By default, the server stops compiling if a parser detects an error. The parsers detect syntax errors in expressions, but they don't detect semantic errors. Semantic errors include an expression referencing a nonexistent column, table, or function, or a value of incorrect type. -`spl.max_error_count` instructs the server to stop parsing if it encounters the specified number of errors in SPL code, or when it encounters an error in SQL code. The default value of `spl.max_error_count` is `10`; the maximum value is `1000`. Setting `spl.max_error_count` to a value of `1` instructs the server to stop parsing when it encounters the first error in either SPL or SQL code. +`spl.max_error_count` instructs the server to stop parsing if it encounters the specified number of errors in SPL code or when it encounters an error in SQL code. The default value of `spl.max_error_count` is `10`. The maximum value is `1000`. Setting `spl.max_error_count` to a value of `1` instructs the server to stop parsing when it encounters the first error in either SPL or SQL code. You can use the `SET` command to specify a value for `spl.max_error_count` for your current session. The syntax is: @@ -18,17 +18,17 @@ You can use the `SET` command to specify a value for `spl.max_error_count` for y SET spl.max_error_count = ``` -Where `number_of_errors` specifies the number of SPL errors that may occur before the server halts the compilation process. For example: +Where `number_of_errors` specifies the number of SPL errors that can occur before the server stops compiling. For example: ``` SET spl.max_error_count = 6 ``` -The example instructs the server to continue past the first five SPL errors it encounters. When the server encounters the sixth error it stops validating, and print six detailed error messages, and one error summary. +The example instructs the server to continue past the first five SPL errors it encounters. When the server encounters the sixth error, it stops validating and prints six detailed error messages and one error summary. -To save time when developing new code, or when importing existing code from another source, you may want to set the `spl.max_error_count` configuration parameter to a relatively high number of errors. +To save time when developing new code or when importing code from another source, you might want to set the `spl.max_error_count` configuration parameter to a relatively high number of errors. -If you instruct the server to continue parsing in spite of errors in the SPL code in a program body, and the parser encounters an error in a segment of SQL code, there may still be errors in any SPL or SQL code that follows the erroneous SQL code. For example, the following function results in two errors: +If you instruct the server to continue parsing in spite of errors in the SPL code in a program body, and the parser encounters an error in a segment of SQL code, there can be more errors in any SPL or SQL code that follows the incorrect SQL code. For example, the following function results in two errors: ```text CREATE FUNCTION computeBonus(baseSalary number) RETURN number AS @@ -49,7 +49,7 @@ LINE 5: total := bonus + 100; ERROR: compilation of SPL function/procedure "computebonus" failed due to 2 errors ``` -The following example adds a `SELECT` statement to the previous example. The error in the `SELECT` statement masks the other errors that follow: +This example adds a `SELECT` statement to the example. The error in the `SELECT` statement masks the other errors that follow. ```text CREATE FUNCTION computeBonus(employeeName number) RETURN number AS diff --git a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/index.mdx index 96fe464bb10..d0dc178355b 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/02_spl_programs/index.mdx @@ -8,9 +8,9 @@ legacyRedirectsGenerated: -SPL is a procedural, block-structured language. There are four different types of programs that can be created using SPL, namely *procedures*, *functions*, *triggers*, and *packages*. +SPL is a procedural, block-structured language. You can create four different types of programs using SPL: *procedures*, *functions*, *triggers*, and *packages*. -In addition, SPL is used to create subprograms. A *subprogram* refers to a *subprocedure* or a *subfunction*, which are nearly identical in appearance to procedures and functions, but differ in that procedures and functions are *standalone programs*, which are individually stored in the database and can be invoked by other SPL programs or from PSQL. Subprograms can only be invoked from within the standalone program within which they have been created. +In addition, you can use SPL to create subprograms. A *subprogram* refers to a *subprocedure* or a *subfunction*. These are nearly identical in appearance to procedures and functions. They differ in that procedures and functions are *standalone programs*. They are stored individually in the database, and you can invoke them from other SPL programs or from PSQL. You can invoke subprograms only from the standalone program where they were created.
diff --git a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx index 556661e0cff..5ae1a4da519 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx @@ -4,7 +4,7 @@ title: "Declaring a variable" -Generally, all variables used in a block must be declared in the declaration section of the block. A variable declaration consists of a name that is assigned to the variable and its data type. Optionally, the variable can be initialized to a default value in the variable declaration. +Generally, you must declare all variables used in a block in the declaration section of the block. A variable declaration consists of a name that's assigned to the variable and its data type. Optionally, you can initialize the variable to a default value in the variable declaration. The general syntax of a variable declaration is: @@ -16,11 +16,11 @@ The general syntax of a variable declaration is: `type` is the data type assigned to the variable. -`[ := expression ]`, if given, specifies the initial value assigned to the variable when the block is entered. If the clause is not given then the variable is initialized to the SQL `NULL` value. +`[ := expression ]`, if given, specifies the initial value assigned to the variable when the block is entered. If the clause isn't given then the variable is initialized to the SQL `NULL` value. The default value is evaluated every time the block is entered. So, for example, assigning `SYSDATE` to a variable of type `DATE` causes the variable to have the time of the current invocation, not the time when the procedure or function was precompiled. -The following procedure illustrates some variable declarations that utilize defaults consisting of string and numeric expressions. +This procedure shows some variable declarations that use defaults consisting of string and numeric expressions: ```text CREATE OR REPLACE PROCEDURE dept_salary_rpt ( @@ -39,7 +39,7 @@ BEGIN END; ``` -The following output of the above procedure shows that default values in the variable declarations are indeed assigned to the variables. +The following output of the procedure shows that default values in the variable declarations are assigned to the variables: ```text EXEC dept_salary_rpt(20); diff --git a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx index 87d4e58525a..bc08d017640 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx @@ -8,25 +8,32 @@ legacyRedirectsGenerated: -Often, variables are declared in SPL programs that are used to hold values from tables in the database. In order to ensure compatibility between the table columns and the SPL variables, the data types of the two should be the same. +Often, variables are declared in SPL programs that are used to hold values from tables in the database. To ensure compatibility between the table columns and the SPL variables, make sure their data types are the same. -However, as quite often happens, a change might be made to the table definition. If the data type of the column is changed, the corresponding change may be required to the variable in the SPL program. +However, often a change is made to the table definition. If the data type of the column is changed, you might need to make the corresponding change to the variable in the SPL program. -Instead of coding the specific column data type into the variable declaration the column attribute, `%TYPE`, can be used instead. A qualified column name in dot notation or the name of a previously declared variable must be specified as a prefix to `%TYPE`. The data type of the column or variable prefixed to `%TYPE` is assigned to the variable being declared. If the data type of the given column or variable changes, the new data type is associated with the variable without the need to modify the declaration code. +Instead of coding the specific column data type into the variable declaration, you can use the column attribute `%TYPE`. Specify a qualified column name in dot notation or the name of a previously declared variable as a prefix to `%TYPE`. The data type of the column or variable prefixed to `%TYPE` is assigned to the variable being declared. If the data type of the given column or variable changes, the new data type is associated with the variable, and you don't need to modify the declaration code. !!! Note - The `%TYPE` attribute can be used with formal parameter declarations as well. + You can use the `%TYPE` attribute with formal parameter declarations as well. ```text { { | }. | }%TYPE; ``` -`name` is the identifier assigned to the variable or formal parameter that is being declared. `column` is the name of a column in `table` or `view`. `variable` is the name of a variable that was declared prior to the variable identified by `name`. +- `name` is the identifier assigned to the variable or formal parameter that's being declared. +- `column` is the name of a column in `table` or `view`. +- `variable` is the name of a variable that was declared prior to the variable identified by `name`. !!! Note - The variable does not inherit any of the column’s other attributes such as might be specified on the column with the `NOT NULL` clause or the `DEFAULT` clause. + The variable doesn't inherit any of the column’s other attributes that you specify on the column with the `NOT NULL` clause or the `DEFAULT` clause. -In the following example a procedure queries the `emp` table using an employee number, displays the employee’s data, finds the average salary of all employees in the department to which the employee belongs, and then compares the chosen employee’s salary with the department average. +In this example, a procedure: + +- Queries the `emp` table using an employee number +- Displays the employee’s data +- Finds the average salary of all employees in the department to which the employee belongs +- Compares the chosen employee’s salary with the department average ```text CREATE OR REPLACE PROCEDURE emp_sal_query ( @@ -62,7 +69,7 @@ BEGIN END; ``` -Instead of the above, the procedure could be written as follows without explicitly coding the `emp` table data types into the declaration section of the procedure. +Alternatively, you can write the procedure without explicitly coding the `emp` table data types into the declaration section of the procedure: ```text CREATE OR REPLACE PROCEDURE emp_sal_query ( @@ -98,12 +105,9 @@ BEGIN END; ``` -!!! Note - `p_empno` shows an example of a formal parameter defined using `%TYPE`. - -`v_avgsal` illustrates the usage of `%TYPE` referring to another variable instead of a table column. +`p_empno` shows an example of a formal parameter defined using `%TYPE`. `v_avgsal` shows the use of `%TYPE` referring to another variable instead of a table column. -The following is sample output from executing this procedure. +The following is sample output from executing this procedure: ```text EXEC emp_sal_query(7698); diff --git a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx index e99ea3d2526..dc6c06b4e89 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx @@ -8,9 +8,9 @@ legacyRedirectsGenerated: -The `%TYPE` attribute provides an easy way to create a variable dependent upon a column’s data type. Using the `%ROWTYPE` attribute, you can define a record that contains fields that correspond to all columns of a given table. Each field takes on the data type of its corresponding column. The fields in the record don't inherit any of the columns’ other attributes such as might be specified with the `NOT NULL` clause or the `DEFAULT` clause. +The `%TYPE` attribute provides an easy way to create a variable that depends on a column's data type. Using the `%ROWTYPE` attribute, you can define a record that contains fields that correspond to all columns of a given table. Each field takes on the data type of its corresponding column. The fields in the record don't inherit any of the columns' other attributes like those specified with the `NOT NULL` clause or the `DEFAULT` clause. -A *record* is a named, ordered collection of fields. A *field* is similar to a variable; it has an identifier and data type, but has the additional property of belonging to a record, and must be referenced using dot notation with the record name as its qualifier. +A *record* is a named, ordered collection of fields. A *field* is similar to a variable. It has an identifier and data type but has the additional property of belonging to a record. You must refereence it using dot notation with the record name as its qualifier. You can use the `%ROWTYPE` attribute to declare a record. The `%ROWTYPE` attribute is prefixed by a table name. Each column in the named table defines an identically named field in the record with the same data type as the column. @@ -18,7 +18,10 @@ You can use the `%ROWTYPE` attribute to declare a record. The `%ROWTYPE` attribu
%ROWTYPE; ``` -`record` is an identifier assigned to the record. `table` is the name of a table (or view) whose columns are to define the fields in the record. The following example shows how the `emp_sal_query` procedure from the prior section can be modified to use `emp%ROWTYPE` to create a record named `r_emp` instead of declaring individual variables for the columns in `emp`. +- `record` is an identifier assigned to the record. +- `table` is the name of a table or view whose columns define the fields in the record. + +This example shows how you can modify the `emp_sal_query` procedure from [Using %TYPE in variable declarations](02_using__type_in_variable_declarations) to use `emp%ROWTYPE` to create a record named `r_emp` instead of declaring individual variables for the columns in `emp`: ```text CREATE OR REPLACE PROCEDURE emp_sal_query ( diff --git a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx index d53804de4f5..43e63524ae7 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx @@ -8,9 +8,9 @@ legacyRedirectsGenerated: -Records can be declared based upon a table definition using the `%ROWTYPE` attribute as shown in [Using %ROWTYPE in Record Declarations](03_using__row_type_in_record_declarations). This section describes how a new record structure can be defined that is not tied to any particular table definition. +You can declare records based on a table definition using the `%ROWTYPE` attribute, as shown in [Using %ROWTYPE in record declarations](03_using__row_type_in_record_declarations). You can also define a new record structure that isn't tied to a particular table definition. -The `TYPE IS RECORD` statement is used to create the definition of a record type. A *record type* is a definition of a record comprised of one or more identifiers and their corresponding data types. A record type cannot, by itself, be used to manipulate data. +You use the `TYPE IS RECORD` statement to create the definition of a record type. A *record type* is a definition of a record made up of one or more identifiers and their corresponding data types. You can't use a record type by itself to manipulate data. The syntax for a `TYPE IS RECORD` statement is: @@ -26,33 +26,22 @@ Where `fields` is a comma-separated list of one or more field definitions of the Where: -`rec_type` +- `rec_type` is an identifier assigned to the record type. +- `field_name` is the identifier assigned to the field of the record type. +- `data_type` specifies the data type of `field_name`. +- The `DEFAULT` clause assigns a default data value for the corresponding field. The data type of the default expression must match the data type of the column. If you don't specify a default, then the default is `NULL`. - `rec_type` is an identifier assigned to the record type. +A *record variable* or *record* is an instance of a record type. A record is declared from a record type. The properties of the record such as its field names and types are inherited from the record type. -`field_name` - - `field_name` is the identifier assigned to the field of the record type. - -`data_type` - - `data_type` specifies the data type of `field_name`. - -`DEFAULT default_value` - - The `DEFAULT` clause assigns a default data value for the corresponding field. The data type of the default expression must match the data type of the column. If no default is specified, then the default is `NULL`. - -A *record variable* or simply put, a *record*, is an instance of a record type. A record is declared from a record type. The properties of the record such as its field names and types are inherited from the record type. - -The following is the syntax for a record declaration. +The following is the syntax for a record declaration: ```text ``` -`record` is an identifier assigned to the record variable. `rectype` is the identifier of a previously defined record type. Once declared, a record can then be used to hold data. +`record` is an identifier assigned to the record variable. `rectype` is the identifier of a previously defined record type. Once declared, you can't then use a record to hold data. -Dot notation is used to make reference to the fields in the record. +Use dot notation to reference the fields in the record: ```text . @@ -60,7 +49,7 @@ Dot notation is used to make reference to the fields in the record. `record` is a previously declared record variable and `field` is the identifier of a field belonging to the record type from which `record` is defined. -The `emp_sal_query` is again modified – this time using a user-defined record type and record variable. +This `emp_sal_query` procedure uses a user-defined record type and record variable: ```text CREATE OR REPLACE PROCEDURE emp_sal_query ( @@ -99,9 +88,9 @@ BEGIN END; ``` -Note that instead of specifying data type names, the `%TYPE` attribute can be used for the field data types in the record type definition. +Instead of specifying data type names, you can use the `%TYPE` attribute for the field data types in the record type definition. -The following is the output from executing this stored procedure. +The following is the output from executing this stored procedure: ```text EXEC emp_sal_query(7698); diff --git a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/index.mdx index 13a4ec61b59..64675583a09 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/03_variable_declarations/index.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -SPL is a block-structured language. The first section that can appear in a block is the declaration. The declaration contains the definition of variables, cursors, and other types that can be used in SPL statements contained in the block. +SPL is a block-structured language. The first section that can appear in a block is the declaration. The declaration contains the definition of variables, cursors, and other types that you can use in SPL statements contained in the block.
diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/01_assignment.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/01_assignment.mdx index 663bb0e30d4..162b08758ab 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/01_assignment.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/01_assignment.mdx @@ -4,7 +4,7 @@ title: "Assignment" -The assignment statement sets a variable or a formal parameter of mode `OUT` or `IN OUT` specified on the left side of the assignment, `:=`, to the evaluated expression specified on the right side of the assignment. +The assignment statement sets a variable or a formal parameter of mode `OUT` or `IN OUT` specified on the left side of the assignment `:=` to the evaluated expression specified on the right side of the assignment. ```text := ; @@ -12,9 +12,9 @@ The assignment statement sets a variable or a formal parameter of mode `OUT` or `variable` is an identifier for a previously declared variable, `OUT` formal parameter, or `IN OUT` formal parameter. -`expression` is an expression that produces a single value. The value produced by the expression must have a compatible data type with that of `variable`. +`expression` is an expression that produces a single value. The value produced by the expression must have a data type compatible with that of `variable`. -The following example shows the typical use of assignment statements in the executable section of the procedure. +This example shows the typical use of assignment statements in the executable section of the procedure: ```text CREATE OR REPLACE PROCEDURE dept_salary_rpt ( diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/02_delete.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/02_delete.mdx index cb0e6454d52..4326eb0fdc5 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/02_delete.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/02_delete.mdx @@ -4,9 +4,9 @@ title: "DELETE" -The `DELETE` command (available in the SQL language) can also be used in SPL programs. +You can use the `DELETE` command available in the SQL language in SPL programs. -An expression in the SPL language can be used wherever an expression is allowed in the SQL `DELETE` command. Thus, SPL variables and parameters can be used to supply values to the delete operation. +You can use an expression in the SPL language wherever an expression is allowed in the SQL `DELETE` command. Thus, you can use SPL variables and parameters to supply values to the delete operation. ```text CREATE OR REPLACE PROCEDURE emp_delete ( @@ -24,9 +24,9 @@ BEGIN END; ``` -The `SQL%FOUND` conditional expression returns `TRUE` if a row is deleted, `FALSE` otherwise. See [Obtaining the Result Status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions. +The `SQL%FOUND` conditional expression returns `TRUE` if a row is deleted, `FALSE` otherwise. See [Obtaining the result status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions. -The following shows the deletion of an employee using this procedure. +This example deletes an employee using this procedure: ```text EXEC emp_delete(9503); @@ -41,4 +41,4 @@ SELECT * FROM emp WHERE empno = 9503; ``` !!! Note - The `DELETE` command can be included in a `FORALL` statement. A `FORALL` statement allows a single `DELETE` command to delete multiple rows from values supplied in one or more collections. See [Using the FORALL Statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information on the `FORALL` statement. + You can include the `DELETE` command in a `FORALL` statement. A `FORALL` statement allows a single `DELETE` command to delete multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/03_insert.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/03_insert.mdx index 4ee4ae25c97..afe2356e887 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/03_insert.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/03_insert.mdx @@ -4,11 +4,11 @@ title: "INSERT" -The `INSERT` command available in the SQL language can also be used in SPL programs. +You can use the `INSERT` command available in the SQL language in SPL programs. -An expression in the SPL language can be used wherever an expression is allowed in the SQL `INSERT` command. Thus, SPL variables and parameters can be used to supply values to the insert operation. +You can use an expression in the SPL language wherever an expression is allowed in the SQL `INSERT` command. Thus, you can use SPL variables and parameters to supply values to the insert operation. -The following is an example of a procedure that performs an insert of a new employee using data passed from a calling program. +This example is a procedure that inserts a new employee using data passed from a calling program: ```text CREATE OR REPLACE PROCEDURE emp_insert ( @@ -52,9 +52,9 @@ EXCEPTION END; ``` -If an exception occurs all database changes made in the procedure are automatically rolled back. In this example the `EXCEPTION` section with the `WHEN OTHERS` clause catches all exceptions. Two variables are displayed. `SQLCODE` is a number that identifies the specific exception that occurred. `SQLERRM` is a text message explaining the error. See [Exception Handling](../05_control_structures/07_exception_handling/#exception_handling) for more information on exception handling. +If an exception occurs, all database changes made in the procedure are rolled back. In this example, the `EXCEPTION` section with the `WHEN OTHERS` clause catches all exceptions. Two variables are displayed. `SQLCODE` is a number that identifies the specific exception that occurred. `SQLERRM` is a text message explaining the error. See [Exception handling](../05_control_structures/07_exception_handling/#exception_handling) for more information. -The following shows the output when this procedure is executed. +The following shows the output when this procedure is executed: ```text EXEC emp_insert(9503,'PETERSON','ANALYST',7902,'31-MAR-05',5000,NULL,40); @@ -78,4 +78,4 @@ SELECT * FROM emp WHERE empno = 9503; ``` !!! Note - The `INSERT` command can be included in a `FORALL` statement. A `FORALL` statement allows a single `INSERT` command to insert multiple rows from values supplied in one or more collections. See [Using the FORALL Statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information on the `FORALL` statement. + You can include the `INSERT` command in a `FORALL` statement. A `FORALL` statement allows a single `INSERT` command to insert multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/04_null.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/04_null.mdx index 8730e8e7484..d4de7baaac1 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/04_null.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/04_null.mdx @@ -10,7 +10,7 @@ The simplest statement is the `NULL` statement. This statement is an executable NULL; ``` -The following is the simplest possible valid SPL program. +The following is the simplest possible valid SPL program: ```text BEGIN @@ -18,9 +18,7 @@ BEGIN END; ``` -The `NULL` statement can act as a placeholder where an executable statement is required such as in a branch of an `IF-THEN-ELSE` statement. - -For example: +The `NULL` statement can act as a placeholder where an executable statement is required such as in a branch of an `IF-THEN-ELSE` statement. For example: ```text CREATE OR REPLACE PROCEDURE divide_it ( diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx index 1b03c0382cb..2843ec0d8ab 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause.mdx @@ -4,9 +4,9 @@ title: "Using the RETURNING INTO clause" -The `INSERT, UPDATE`, and `DELETE` commands may be appended by the optional `RETURNING INTO` clause. This clause allows the SPL program to capture the newly added, modified, or deleted values from the results of an `INSERT, UPDATE`, or `DELETE` command, respectively. +You can append the `INSERT`, `UPDATE`, and `DELETE` commands with the optional `RETURNING INTO` clause. This clause allows the SPL program to capture the newly added, modified, or deleted values from the results of an `INSERT`, `UPDATE`, or `DELETE` command, respectively. -The following is the syntax. +The following is the syntax: ```text { | | } @@ -14,14 +14,20 @@ The following is the syntax. INTO { | [, ] ...}; ``` -`insert` is a valid `INSERT` command. `update` is a valid `UPDATE` command. `delete` is a valid `DELETE` command. If `*` is specified, then the values from the row affected by the `INSERT, UPDATE`, or `DELETE` command are made available for assignment to the record or fields to the right of the `INTO` keyword. (Note that the use of `*` is an EDB Postgres Advanced Server extension and is not compatible with Oracle databases.) `expr_1, expr_2...` are expressions evaluated upon the row affected by the `INSERT, UPDATE`, or `DELETE` command. The evaluated results are assigned to the record or fields to the right of the `INTO` keyword. `record` is the identifier of a record that must contain fields that match in number and order, and are data type compatible with the values in the `RETURNING` clause. `field_1, field_2,...` are variables that must match in number and order, and are data type compatible with the set of values in the `RETURNING` clause. +- `insert` is a valid `INSERT` command. +- `update` is a valid `UPDATE` command. +- `delete` is a valid `DELETE` command. +- If you specify `*`, then the values from the row affected by the `INSERT`, `UPDATE`, or `DELETE` command are made available for assignment to the record or fields to the right of the `INTO` keyword. (The use of `*` is an EDB Postgres Advanced Server extension and isn't compatible with Oracle databases.) +- `expr_1, expr_2...` are expressions evaluated upon the row affected by the `INSERT`, `UPDATE`, or `DELETE` command. The evaluated results are assigned to the record or fields to the right of the `INTO` keyword. +- `record` is the identifier of a record that must contain fields that match in number and order and are data-type compatible with the values in the `RETURNING` clause. +- `field_1, field_2,...` are variables that must match in number and order and are data-type compatible with the set of values in the `RETURNING` clause. -If the `INSERT, UPDATE`, or `DELETE` command returns a result set with more than one row, then an exception is thrown with `SQLCODE 01422, query returned more than one row`. If no rows are in the result set, then the variables following the `INTO` keyword are set to null. +If the `INSERT`, `UPDATE`, or `DELETE` command returns a result set with more than one row, then an exception is thrown with `SQLCODE 01422, query returned more than one row`. If no rows are in the result set, then the variables following the `INTO` keyword are set to null. !!! Note - There is a variation of `RETURNING INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that is returned into a collection. See [Using the BULK COLLECT Clause](../12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information on the `BULK COLLECT` clause. + A variation of `RETURNING INTO` using the `BULK COLLECT` clause allows a result set of more than one row that's returned into a collection. See [Using the BULK COLLECT clause](../12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information. -The following example is a modification of the `emp_comp_update` procedure introduced in [UPDATE](07_update/#update), with the addition of the `RETURNING INTO` clause. +This example modifies the `emp_comp_update` procedure introduced in [UPDATE](07_update/#update). It adds the `RETURNING INTO` clause: ```text CREATE OR REPLACE PROCEDURE emp_comp_update ( @@ -66,7 +72,7 @@ BEGIN END; ``` -The following is the output from this procedure (assuming employee `9503` created by the `emp_insert` procedure still exists within the table). +The following is the output from this procedure, assuming employee `9503` created by the `emp_insert` procedure still exists in the table: ```text EXEC emp_comp_update(9503, 6540, 1200); @@ -79,7 +85,7 @@ New Salary : 6540.00 New Commission : 1200.00 ``` -The following example is a modification of the `emp_delete` procedure, with the addition of the `RETURNING INTO` clause using record types. +This example modifies the `emp_delete` procedure, adding the `RETURNING INTO` clause using record types: ```text CREATE OR REPLACE PROCEDURE emp_delete ( @@ -109,7 +115,7 @@ BEGIN END; ``` -The following is the output from this procedure. +The following is the output from this procedure: ```text EXEC emp_delete(9503); diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/06_select_into.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/06_select_into.mdx index d277aacf4e7..d51f540621d 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/06_select_into.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/06_select_into.mdx @@ -4,12 +4,12 @@ title: "SELECT INTO" -The `SELECT INTO` statement is an SPL variation of the SQL `SELECT` command, the differences being: +The `SELECT INTO` statement is an SPL variation of the SQL `SELECT` command. The differences are: -- That `SELECT INTO` is designed to assign the results to variables or records where they can then be used in SPL program statements. +- `SELECT INTO` assigns the results to variables or records where they can then be used in SPL program statements. - The accessible result set of `SELECT INTO` is at most one row. -Other than the above, all of the clauses of the `SELECT` command such as `WHERE, ORDER BY, GROUP BY, HAVING`, etc. are valid for `SELECT INTO`. The following are the two variations of `SELECT INTO`. +Other than these differences, all of the clauses of the `SELECT` command, such as `WHERE`, `ORDER BY`, `GROUP BY`, and `HAVING`, are valid for `SELECT INTO`. The following are the two variations of `SELECT INTO`: ```text SELECT INTO FROM ...; @@ -21,18 +21,18 @@ SELECT INTO FROM ...; SELECT * INTO FROM
...; ``` -`record` is a record variable that has previously been declared. +`record` is a record variable that was previously declared. -If the query returns zero rows, null values are assigned to the target(s). If the query returns multiple rows, the first row is assigned to the target(s) and the rest are discarded. (Note that "the first row" is not well-defined unless you’ve used `ORDER BY.`) +If the query returns zero rows, null values are assigned to the targets. If the query returns multiple rows, the first row is assigned to the targets and the rest are discarded. ("The first row" isn't well-defined unless you used `ORDER BY.`) !!! Note - - In either cases, where no row is returned or more than one row is returned, SPL throws an exception. + - In either case, where no row is returned or more than one row is returned, SPL throws an exception. - - There is a variation of `SELECT INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that is returned into a collection. See [SELECT BULK COLLECT](../12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/#select_bulk_collect) for more information on using the `BULK COLLECT` clause with the `SELECT INTO` statement. + - There is a variation of `SELECT INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that's returned into a collection. See [SELECT BULK COLLECT](../12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/#select_bulk_collect) for more information. -You can use the `WHEN NO_DATA_FOUND` clause in an `EXCEPTION` block to determine whether the assignment was successful (that is, at least one row was returned by the query). +You can use the `WHEN NO_DATA_FOUND` clause in an `EXCEPTION` block to determine whether the assignment was successful, that is, at least one row was returned by the query. -This version of the `emp_sal_query` procedure uses the variation of `SELECT INTO` that returns the result set into a record. Also note the addition of the `EXCEPTION` block containing the `WHEN NO_DATA_FOUND` conditional expression. +This version of the `emp_sal_query` procedure uses the variation of `SELECT INTO` that returns the result set into a record. It also uses the `EXCEPTION` block containing the `WHEN NO_DATA_FOUND` conditional expression. ```text CREATE OR REPLACE PROCEDURE emp_sal_query ( @@ -66,7 +66,7 @@ EXCEPTION END; ``` -If the query is executed with a non-existent employee number the results appear as follows. +If the query is executed with a nonexistent employee number, the results appear as follows: ```text EXEC emp_sal_query(0); @@ -74,9 +74,9 @@ EXEC emp_sal_query(0); Employee # 0 not found ``` -Another conditional clause of use in the `EXCEPTION` section with `SELECT INTO` is the `TOO_MANY_ROWS` exception. If more than one row is selected by the `SELECT INTO` statement an exception is thrown by SPL. +Another conditional clause useful in the `EXCEPTION` section with `SELECT INTO` is the `TOO_MANY_ROWS` exception. If more than one row is selected by the `SELECT INTO` statement, SPL throws an exception. -When the following block is executed, the `TOO_MANY_ROWS` exception is thrown since there are many employees in the specified department. +When the following block is executed, the `TOO_MANY_ROWS` exception is thrown since there are many employees in the specified department: ```text DECLARE @@ -93,5 +93,4 @@ More than one employee found First employee returned is ADAMS ``` -!!! Note - See [Exception Handling](../05_control_structures/07_exception_handling/#exception_handling) for more information on exception handling. +See [Exception handling](../05_control_structures/07_exception_handling/#exception_handling) for information on exception handling. diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/07_update.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/07_update.mdx index 560bf25d6f7..6be9a47e417 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/07_update.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/07_update.mdx @@ -4,9 +4,9 @@ title: "UPDATE" -The `UPDATE` command available in the SQL language can also be used in SPL programs. +You can use the `UPDATE` command available in the SQL language in SPL programs. -An expression in the SPL language can be used wherever an expression is allowed in the SQL `UPDATE` command. Thus, SPL variables and parameters can be used to supply values to the update operation. +You can use an expression in the SPL language wherever an expression is allowed in the SQL `UPDATE` command. Thus, you can use SPL variables and parameters to supply values to the update operation. ```text CREATE OR REPLACE PROCEDURE emp_comp_update ( @@ -28,9 +28,9 @@ BEGIN END; ``` -The `SQL%FOUND` conditional expression returns `TRUE` if a row is updated, `FALSE` otherwise. See [Obtaining the Result Status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions. +The `SQL%FOUND` conditional expression returns `TRUE` if a row is updated, `FALSE` otherwise. See [Obtaining the result status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions. -The following shows the update on the employee using this procedure. +The following shows the update on the employee using this procedure: ```text EXEC emp_comp_update(9503, 6540, 1200); @@ -48,4 +48,4 @@ empno | ename | job | mgr | hiredate | sal | comm | deptno ``` !!! Note - The `UPDATE` command can be included in a `FORALL` statement. A `FORALL` statement allows a single `UPDATE` command to update multiple rows from values supplied in one or more collections. See [Using the FORALL Statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information on the `FORALL` statement. + You can include the `UPDATE` command in a `FORALL` statement. A `FORALL` statement allows a single `UPDATE` command to update multiple rows from values supplied in one or more collections. See [Using the FORALL statement](../12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information. diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx index 1c78a48053f..e685797d3e0 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status.mdx @@ -4,9 +4,9 @@ title: "Obtaining the result status" -There are several attributes that can be used to determine the effect of a command. `SQL%FOUND` is a Boolean that returns `TRUE` if at least one row was affected by an `INSERT, UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved one or more rows. +You can use several attributes to determine the effect of a command. `SQL%FOUND` is a Boolean that returns `TRUE` if at least one row was affected by an `INSERT`, `UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved one or more rows. -The following anonymous block inserts a row and then displays the fact that the row has been inserted. +The following anonymous block inserts a row and then displays the fact that the row was inserted: ```text BEGIN @@ -20,7 +20,7 @@ END; Row has been inserted ``` -`SQL%ROWCOUNT` provides the number of rows affected by an `INSERT, UPDATE, DELETE`, or `SELECT INTO` command. The `SQL%ROWCOUNT` value is returned as a `BIGINT` data type. The following example updates the row that was just inserted and displays `SQL%ROWCOUNT`. +`SQL%ROWCOUNT` provides the number of rows affected by an `INSERT`, `UPDATE`, `DELETE`, or `SELECT INTO` command. The `SQL%ROWCOUNT` value is returned as a `BIGINT` data type. The following example updates the row that was just inserted and displays `SQL%ROWCOUNT`: ```text BEGIN @@ -31,7 +31,7 @@ END; # rows updated: 1 ``` -`SQL%NOTFOUND` is the opposite of `SQL%FOUND`. `SQL%NOTFOUND` returns `TRUE` if no rows were affected by an `INSERT, UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved no rows. +`SQL%NOTFOUND` is the opposite of `SQL%FOUND`. `SQL%NOTFOUND` returns `TRUE` if no rows were affected by an `INSERT`, `UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved no rows. ```text BEGIN diff --git a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/index.mdx b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/index.mdx index 315c88ffe0f..fcf7ad7dc09 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/04_basic_statements/index.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -This section begins the discussion of the programming statements that can be used in an SPL program. +You can use several programming statements in an SPL program.
From 3484dfe93deb4c61eea4116e60b217e212abd202 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 18 Nov 2022 06:11:57 -0500 Subject: [PATCH 29/32] BigAnimal: updates to quick start and pg version number rewrote added sentence avoiding the 14 vs 15 issue --- .../biganimal/release/free_trial/index.mdx | 4 ++-- .../release/free_trial/quickstart.mdx | 21 +++++++++++-------- 2 files changed, 14 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/biganimal/release/free_trial/index.mdx b/product_docs/docs/biganimal/release/free_trial/index.mdx index e00c580fa78..7a1107f0107 100644 --- a/product_docs/docs/biganimal/release/free_trial/index.mdx +++ b/product_docs/docs/biganimal/release/free_trial/index.mdx @@ -17,7 +17,7 @@ The free trial provides a subset of the full-featured BigAnimal environment so t ## What you get as part of the free trial - **The latest & greatest PostgreSQL and EDB Postgres Advanced Server databases.** - - [PostgreSQL 14](https://www.enterprisedb.com/blog/cool-new-contributions-postgresql-14) is more flexible, more secure, and faster than ever ([release notes](https://www.postgresql.org/docs/14/release.html)). + - [PostgreSQL 14](https://www.enterprisedb.com/blog/cool-new-contributions-postgresql-14) is more flexible, more secure, and faster than ever ([release notes](https://www.postgresql.org/docs/14/release.html)). Or, try out BigAnimal's beta support of PostgresSQL 15 ([release notes](https://www.postgresql.org/docs/15/release.html)). - [EDB Postgres Advanced Server 14](https://www.enterprisedb.com/docs/epas/latest/epas_rel_notes/) builds on PostgreSQL 14 with a host of features for Oracle database compatibility, security, and usability ([more on Oracle database compatibility](/epas/latest/epas_compat_ora_dev_guide/)). - **One active cluster, unlimited inactive ones.** @@ -49,7 +49,7 @@ Accounts are free, and registration takes less than a minute. The free trial allows you to create a database cluster hosted on BigAnimal to try for 14 days. While the trial allows only one cluster to be active at a time, you are free to delete your cluster and create a new one. It's even possible to restore any cluster you've previously deleted. -BigAnimal offers both standard PostgreSQL and EDB Postgres Advanced Server clusters. You can try out either using the latest PostgreSQL version (14) or one of the previous supported versions (11–13). Other configuration options are limited for the free trial. +BigAnimal offers both standard PostgreSQL and EDB Postgres Advanced Server clusters. You can try out either using the latest version or one of the previous supported versions starting at version 11. Other configuration options are limited for the free trial. There are several equivalent ways to create a cluster: diff --git a/product_docs/docs/biganimal/release/free_trial/quickstart.mdx b/product_docs/docs/biganimal/release/free_trial/quickstart.mdx index 0d06d7760d8..8c6cc3957ff 100644 --- a/product_docs/docs/biganimal/release/free_trial/quickstart.mdx +++ b/product_docs/docs/biganimal/release/free_trial/quickstart.mdx @@ -23,22 +23,25 @@ Then, use your newly created account to access the [BigAnimal free trial portal] 1. Select the **Clusters** link on the left to navigate to the [Clusters](https://portal.biganimal.com/clusters) page. -2. Select the **Create New Cluster** button. +1. Select the **Create New Cluster** button. You should now find yourself at the [Create Cluster page](https://portal.biganimal.com/create-cluster). -3. Enter `AWS PostgreSQL cluster` in the **Cluster Name** field. -4. Enter a strong, memorable password in the **Password** field. +1. Select **Single Node** as your cluster type. +1. Select **AWS** for **Provider**. +1. Select **Next: Cluster Settings**. +1. Enter `AWS PostgreSQL cluster` in the **Cluster Name** field. +1. Enter a strong, memorable password in the **Password** field. This is the admin password for the cluster. -5. Select **PostgreSQL** for **Database Type** +1. Select **PostgreSQL** for **Database Type** This gives you an official build of PostgreSQL. -6. Select **14** for **Postgres Version**. -4. Select **AWS** for **Provider**. -5. Select **US East 1** for **Region**. -6. For **Instance Type** and **Storage**, only one set of options is available in the trial. Select each option. -7. Select **Create Cluster**. You'll be brought back to the Clusters page with your newly configured cluster now populating the list. It usually takes a minute or two for your cluster to be ready but can take up to an hour. A progress bar is shown near the right. +1. Select **14** for **Postgres Version**. + +1. Select **US East 1** for **Region**. +1. For **Instance Type** and **Storage**, only one set of options is available in the trial. Select each option. +1. Select **Create Cluster**. You'll be brought back to the Clusters page with your newly configured cluster now populating the list. It usually takes a minute or two for your cluster to be ready but can take up to an hour. A progress bar is shown near the right. ### Managing your cluster From ee4aa31f6c76c416f9bd89a382dc26777f2c56bd Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 18 Nov 2022 08:34:10 -0500 Subject: [PATCH 30/32] fixed broken link --- .../01_introduction/02_edb_redwood_raw_names.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx index dcba9cf1783..653cf341308 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx @@ -4,7 +4,7 @@ title: "edb_redwood_raw_names" -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_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 [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 `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. From bb5638d3b2420fad03daf9a189435ca621749797 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 21 Nov 2022 05:37:42 -0500 Subject: [PATCH 31/32] Changed 7.0 to 7.x --- product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx index a0da8c9e81e..404cfca388a 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx @@ -24,7 +24,7 @@ The EDB Postgres Replication Server documentation describes the latest version o To install Replication Server 6.2.x for the first time or to upgrade to the latest Replication Server 6.2.x release from an earlier Replication Server 6.2.x release using the EDB repository, you must use the `--exclude edb-xdb` option with the install or upgrade command. -If the exclude option is not used, Replication Server version 7.0 is +If the exclude option is not used, Replication Server version 7.x is installed. To upgrade: From 017b8c43e04e5aba854c0594cc77b49d5a241fb2 Mon Sep 17 00:00:00 2001 From: scottatchue <87328931+scottatchue@users.noreply.github.com> Date: Mon, 21 Nov 2022 09:50:54 -0500 Subject: [PATCH 32/32] Update index.mdx The title for PgBouncer and Pgpool both had double "with" in it. --- product_docs/docs/efm/4/efm_deploy_arch/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/efm_deploy_arch/index.mdx b/product_docs/docs/efm/4/efm_deploy_arch/index.mdx index b591d1f992e..b39776f9d49 100644 --- a/product_docs/docs/efm/4/efm_deploy_arch/index.mdx +++ b/product_docs/docs/efm/4/efm_deploy_arch/index.mdx @@ -64,7 +64,7 @@ architectures: **Client connect failover** -|Features | Failover Manager with VIP | Failover Manager with client connect failover | Failover Manager with with EDB PgBouncer | Failover Manager with with EDB Pgpool-II | +|Features | Failover Manager with VIP | Failover Manager with client connect failover | Failover Manager with EDB PgBouncer | Failover Manager with EDB Pgpool-II | |---------------------------------------- | ----------------------- | ----------------------------------------- | ----------------------- | ---------------------| |Connection pooling | | | Yes | Yes | |Runs on cloud (no VIP) | | Yes | Yes | Yes |