Ispirer Home Page Database Migration Application Conversion Downloads
Sqlways_db.ini File - Section [Postgre]
This article describes sqlways_db.ini file's [Postgre] section and the options it contains.
| Option name | Description |
|---|---|
| AUTONOMOUS_TRANSACTION | This option controls how to convert procedures and functions with the AUTONOMOUS TRANSACTION pragma to the PostgreSQL database. If this option is set to “comment”, this pragme will be commented out. If this option is set to “DBLINK”, these procedures will be converted to the recursive procedures with dblink to the remote database. An additional script will be generated in which FOREIGN SERVER and USER MAPPING will be created for the current user. This script should be executed as the superuser. Possible values: “DBLINK”, “comment” or Empty. Default value: “comment”/Empty. Usage Example. |
| CASE_INSENS_DATA | This option specifies how to handle case-insensitive data during the conversion process. COLLATION: Generates both deterministic and non-deterministic collations during conversion to preserve case-insensitive behavior. LOWER: Implements case-insensitive comparisons by wrapping both operands in the LOWER() function. This applies to all case-insensitive comparisons except ILIKE, which remains unchanged. Possible values: “Default”, “Collation”, “Lower”. Default value: “Default”. Usage Example. |
| COMMENT_TRANSACTION | This option controls the conversion of transaction statements (commit, rollback, etc). If this option is set to “Yes”, all transactions will be commented out. If this option is set to “No”, all transactions will be left as in the source code. Possible values: “No”, “Yes” or Empty. Default value: “Yes”/Empty. Usage Example. |
| CONV_ALL_PROC_TO_FUNC | This option controls how stored procedures are converted to a PostgreSQL database. If the option is set to “Yes”, then all stored procedures will be converted to functions in PostgreSQL. Possible values: “Yes”, “No” or Empty. Default value: “No”/Empty. Usage Example. |
| CONVERT_TYPE_TO_SCHEMA | This option is used when converting Oracle user-defined types. If this option is set to “Yes” and the type contains a constructor and/or member procedures or functions, a separate schema named after the type is created, and all of its members are placed in that schema. By default, if this option is set to “No”, the original schema is preserved, and the names of the type's procedures and functions are prefixed with the type name. Possible values: “Yes”, “No” or Empty. Default value: “No”/Empty. Usage Example. |
| CURSOR_IN_SELECT | This option controls how cursors in SELECT statements are converted. By default, such cursors are converted using the swf_ret_cur helper function. If this option is set to “JSONB”, the result set returned by the cursor query is converted to the jsonb data type instead. Possible values: “JSONB”, Empty. Default value: Empty. Usage Example. |
| PACKAGE_VAR_CONVERSION | This option specifies how Oracle package variables are converted. By default, all package variables are combined into a single composite type, and access to them is performed through an instance of that type. Constant variables are converted in the same way for all options. temp_table: Stores the composite type instance in a temporary table with a single row. pg_variables: Stores package variable values using the pg_variables extension (pgv_set/pgv_get). Use pgv_free() to clear the variables for the current session. session_config_params: Stores package variable values using the set_config and current_setting functions. Possible values: “pg_variables”, “session_config_params“, “temp_table” or Empty. Default value: “temp_table”/Empty. Usage Example. |
| RETURN_RESULT_FROM_SP_AND_FN | This option controls the conversion of transaction statements (commit, rollback, etc). If this option is set to “Yes”, all transactions will be commented out. If this option is set to “No”, all transactions will be left as in the source code. Possible values: “SETOF”, “REFCURSOR“, “TABLE” or Empty. Default value: “TABLE”/Empty. Usage Example. |
| SECURITY_DEFINER | This option converts adds to PostgreSQL routines SECURITY DEFINER parameter. Note that transaction control statements are not allowed in SECURITY DEFINER routines. Therefore, do not set “COMMENT_TRANSACTION” option to “No” or eliminate this discrepancy manually after conversion. Possible values: “Yes”, “No“. Default value: “No”. Usage Example. |
| DOLLAR_QUOTED_PGSQL_MASK | This option controls the dollar quotation in pgsql. The value specified here will be used instead of “$$” in Pl/PgSQL. Default value: “$$”. |
| USER | This option sets the user account that will be used to connect to the PostgreSQL database. |
| DATABASE | This option sets the database name where the import will be done. |
| TABLESPACE | With this option, you can specify the tablespace name that will be used in CREATE TABLE statements in PostgreSQL. Default value: Empty. |
| USE_SOURCE_TABLESPACE_NAMES | This option defines whether the original tablespace names will be used in the converted object definitions. Possible values: “Yes”, “No” or Empty. Default value: “No” or Empty. |
| PARTITION_ENABLE | This option is available for PostgreSQL version 10 and later and controls whether table partitioning should be migrated or not. To allow table partitions conversion, set this option to “Yes”. If table partitions conversion is not required, the value should be set to “No”. Possible values: “No”, “Yes” or Empty. Default value: “Yes” or Empty. |