Ispirer Ispirer
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

sqlways:command-line:sqlways-ini:postgresql-section [September 24, 2018, 09:41:21 AM]
alexandr.kirpichny
sqlways:command-line:sqlways-ini:postgresql-section [November 16, 2018, 11:06:09 AM] (current)
darya.prikhodkina [Sqlways.ini File - Section [Postgre]]
Line 14: Line 14:
 | **TARGET_VERSION** | This option sets the version number of the database where import will be done. | | **TARGET_VERSION** | This option sets the version number of the database where import will be done. |
 | **BIN** | Specifies the directory where PSQL.exe utility is located. | | **BIN** | Specifies the directory where PSQL.exe utility is located. |
-| **USE_EXPLICIT_CURSORS** | This option controls the way cursors will be converted in PostgreSQL database. If this option is set to "Yes", explicit cursor declaration will be used. If "No", implicit cursor declaration will be used. \\ Possible values: Yes, No. | +| **USE_EXPLICIT_CURSORS** | This option controls the way cursors will be converted in PostgreSQL database. If this option is set to "Yes", explicit cursor declaration will be used. If set to "No", implicit cursor declaration will be used. \\ Possible values: Yes, No. | 
-| **REPLACE_NULL_BYTE_WITH** | In PostgreSQL it is not allowed to insert null byte in not BYTEA data type column. So this option controls how the null byte should be changed to make a correct import. \\ If the data type of the inserted column will be BYTEA, this option will not work for that case. | +| **REPLACE_NULL_BYTE_WITH** | In PostgreSQL it is not allowed to insert null byte in not BYTEA data type column. So this option controls how the null byte should be changed to make a correct import. \\ If the data type of the inserted column is BYTEA, this option will not work for that case. | 
-| **SET_SEARCH_PATH_TO** | This option will add "SET search_path TO" statement in each sql file generated by the SQLWays Wizard tool. To use this option you need just to specify a schema name that will be used in SET search_path TO statement. \\ By default this option is empty. | +| **SET_SEARCH_PATH_TO** | This option will add "SET search_path TO" statement into each sql file generated by the SQLWays Wizard tool. To use this option you need just to specify a schema name that will be used in SET search_path TO statement. \\ By default this option is empty. | 
-| **DATA_LOAD_FORMAT** | This option defines in what format the data from MSSQL database will be extracted and loaded into PostgreSQL database. Possible values - "HEX" and "OCT". | +| **DATA_LOAD_FORMAT** | This option defines the format the data from MSSQL database will be extracted and loaded into PostgreSQL database. Possible values - "HEX" and "OCT". | 
-| **DOLLAR_QUOTED_PGSQL_MASK** | This option controls dollar quotation in the pgsql. The value specified here will be used instead of "$$" in Pl/PgSQL, that is set by default. | +| **DOLLAR_QUOTED_PGSQL_MASK** | This option controls dollar quotation in the pgsql. The value specified here will be used instead of "$$" in Pl/PgSQL, which is set by default. | 
-| **MULTIPLE_OUT_REFCURSOR_PARAM** | This option controls the conversion of Oracle multiple OUT refcursor parameters in PostgreSQL. If this option is set to "Yes", OUT REFCURSOR parameters will be converted into OUT REFCURSOR parameters in PostgreSQL. If "No" then Oracle procedure with OUT REFCURSORs parameters will be converted into a function which returns setof refcursors. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes".| +| **MULTIPLE_OUT_REFCURSOR_PARAM** | This option controls the conversion of Oracle multiple OUT refcursor parameters in PostgreSQL. If this option is set to "Yes", OUT REFCURSOR parameters will be converted into OUT REFCURSOR parameters in PostgreSQL. If "No"Oracle procedure with OUT REFCURSORs parameters will be converted into a function which returns setof refcursors. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes".| 
-| **AUTOUPDATE_TIMESTAMP_COLUMN** | This option controls the way how TIMESTAMP column is converted from Sybase ASE into PostgreSQL database. If this option is set to "Yes", then in PostgreSQL 2 triggers will be generatedthey will update information in a column. If this option is set to "No", then it will be a common column of BYTEA data type. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |  USE_TABLE_FUNCTIONS +| **AUTOUPDATE_TIMESTAMP_COLUMN** | This option controls the way how TIMESTAMP column is converted from Sybase ASE to PostgreSQL database. If this option is set to "Yes", then 2 triggers will be generated in PostgreSQL and they will update information in a column. If this option is set to "No", then it will be a common column of BYTEA data type. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |  USE_TABLE_FUNCTIONS 
-| **USE_TABLE_FUNCTIONS** | This option controls how Sybase ASE procedures that return result sets will be converted to PostgreSQL. If this option is set to "Yes", then procedures will be converted to table functions. If it is set to "No" then such procedures will be converted to functions that return result sets of defined data type. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |+| **USE_TABLE_FUNCTIONS** | This option controls how Sybase ASE procedures that return result sets will be converted to PostgreSQL. If this option is set to "Yes", then procedures will be converted to table functions. If it is set to "No" then such procedures will be converted into functions that return result sets of defined data type. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
 | **VIRT_COL_SAVE_TBL_NAME** | This option works only for Oracle tables with virtual columns that should be converted to PostgreSQL. And it controls naming of the generated tables and views in PostgreSQL. If this option is set to "Yes" then generated tables will have the same names as in Oracle database and SQLWays will add suffix "_VW" to the generated views. If this option is set to "No", then the suffix "_TBL" will be added to the names of converted tables and generated views will have the same names as Oracle tables with virtual columns. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | | **VIRT_COL_SAVE_TBL_NAME** | This option works only for Oracle tables with virtual columns that should be converted to PostgreSQL. And it controls naming of the generated tables and views in PostgreSQL. If this option is set to "Yes" then generated tables will have the same names as in Oracle database and SQLWays will add suffix "_VW" to the generated views. If this option is set to "No", then the suffix "_TBL" will be added to the names of converted tables and generated views will have the same names as Oracle tables with virtual columns. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
-| **ROWNUM_TO_GENERATE_SERIES** | This option controls how Oracle Rownum function will be converted into PostgreSQL database. If this option is set to "Yes" then it will be converted to GENERATE_SERIES. If this option is set to "No", then Oracle Rownum function will be converted to ROW_NUMBER() with OVER clause in PostgreSQL. \\ Possible values - "Yes" or Empty, "No". \\ Default value - "Yes" or Empty.   |+| **ROWNUM_TO_GENERATE_SERIES** | This option controls how Oracle Rownum function will be converted to PostgreSQL database. If this option is set to "Yes"it will be converted to GENERATE_SERIES. If this option is set to "No", then Oracle Rownum function will be converted to ROW_NUMBER() with OVER clause in PostgreSQL. \\ Possible values - "Yes" or Empty, "No". \\ Default value - "Yes" or Empty.   |
 | **CAST_PARAMETERS_IN_CALL** | This option controls whether the parameters in call routine statements should be casted to the appropriate data types in accordance to the routine signature. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | | **CAST_PARAMETERS_IN_CALL** | This option controls whether the parameters in call routine statements should be casted to the appropriate data types in accordance to the routine signature. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
-| **PARTITION_ENABLE** | This option is managed for PostgreSQL versions 10 and later and controls whether table partitioning should be migrated or no. To allow table partitions conversion, set this option to Yes. If table partitions conversion is not required, "No" value should be specified. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes" or Empty. |+| **PARTITION_ENABLE** | This option is available for PostgreSQL version 10 and later and controls whether table partitioning should be migrated or no. To allow table partitions conversion, set this option to Yes. If table partitions conversion is not required, "No" value should be specified. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes" or Empty. |
 | **TABLES_WITH_OIDS** | This option defines whether the tables will be created with OID. OID column is a system column created for each table. It contains the unique identifier for the row of data in the database and can be used as a unique pointer to the exact record in the database. By default this option is set to "Yes". This means that all the CREATE TABLE statements will be created with the WITH OIDS option.   \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | | **TABLES_WITH_OIDS** | This option defines whether the tables will be created with OID. OID column is a system column created for each table. It contains the unique identifier for the row of data in the database and can be used as a unique pointer to the exact record in the database. By default this option is set to "Yes". This means that all the CREATE TABLE statements will be created with the WITH OIDS option.   \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". |
-| **TABLESPACE** | In this option can be specified tablespace name that will be used in CREATE TABLE statements in PostgreSQL. \\ Default value - Empty. | +| **TABLESPACE** | In this option you can specify the tablespace name that will be used in CREATE TABLE statements in PostgreSQL. \\ Default value - Empty. | 
-| **INDEX_TABLESPACE** | In this option can be specified tablespace name that will be used in CREATE INDEX statements in PostgreSQL. \\ Default value - Empty. |+| **INDEX_TABLESPACE** | In this option you can specify the tablespace name that will be used in CREATE INDEX 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. | | **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. |
-| **DATA_MIGRATOR_BIN_DIRECTORY** | This option allows you to specify the path to the folder containing the ISOFDM.exe tool. Usually the path specification is not required as SQLWays automatically searches for the BIN directory. If the text-box is empty, first it searches the PATH variable, then it searches the registry. If it failed to find the path to the ISOFDM.exe, no path is added to the command and system may return the error on the command execution. \\ Default value - Empty. |+| **DATA_MIGRATOR_BIN_DIRECTORY** | This option allows you to specify the path to the folder which contains the ISOFDM.exe tool. Usually the path specification is not required as SQLWays automatically searches for the BIN directory. If the text-box is empty, first it will search for the PATH variable, then it will search the registry. If it fails to find the path to the ISOFDM.exe, no path will be added to the command and system may return the error on the command execution. \\ Default value - Empty. |
  
  
sqlways/command-line/sqlways-ini/postgresql-section.txt · Last modified: November 16, 2018, 11:06:09 AM by darya.prikhodkina
 
© 1999-2019, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement