Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:mysql-section [September 07, 2018, 01:12:54 PM]
alexandr.kirpichny
sqlways:command-line:sqlways-ini:mysql-section [October 26, 2018, 12:54:05 PM] (current)
darya.prikhodkina [Sqlways.ini File - Section [MYSQL]]
Line 8: Line 8:
 ^  Option name  ^ Description  ^  ^  Option name  ^ Description  ^ 
 | **BIN** | Specifies the directory where MySQL utilities are located. | | **BIN** | Specifies the directory where MySQL utilities are located. |
-| **HOST** | Specifies a remote host name where a target MySQL database resides. |+| **HOST** | Specifies a remote host name where a target MySQL database is located. |
 | **DATABASE** | Specifies the database name which is used in generated scripts for MySQL. | | **DATABASE** | Specifies the database name which is used in generated scripts for MySQL. |
 | **PORT** | This option sets port number that will be used to connect to MySQL database.   | | **PORT** | This option sets port number that will be used to connect to MySQL database.   |
-| **TARGET_VERSION** | Specifies the target version of the MySQL database. If this option is empty the latest MySQL database version will be used. \\ Note: According to the version number conversion results may be different. |+| **TARGET_VERSION** | Specifies the target version of the MySQL database. If this option is empty the latest MySQL database version will be used. \\ Note: According to the version number conversion results may differ. |
 | **USER** | Specifies the user name which is used in generated scripts for MySQL. | | **USER** | Specifies the user name which is used in generated scripts for MySQL. |
 | **PWD** | Specifies the user password which is used in generated scripts for MySQL. | | **PWD** | Specifies the user password which is used in generated scripts for MySQL. |
-| **TABLE_TYPE** | This option specifies the table type which is used when creating tables in a MySQL database. MySQL supports two different kinds of tables: transaction-safe tables (InnoDB and BDB) and not transaction-safe tables (HEAP, ISAM, MERGE, and MyISAM). \\ For example, when table_type=InnoDB is selected, SQLWays generates TYPE=InnoDB clause in CREATE TABLE statements for MySQL. | +| **TABLE_TYPE** | This option specifies the table type which is used when creating tables in a MySQL database. MySQL supports two kinds of tables: transaction-safe tables (InnoDB and BDB) and not transaction-safe tables (HEAP, ISAM, MERGE, and MyISAM). \\ For example, when table_type=InnoDB is selected, SQLWays generates TYPE=InnoDB clause in CREATE TABLE statements for MySQL. | 
-| **IMPORT_FROM_CLIENT** | If Yes is specified, the LOCAL keyword is generated for MySQL LOAD DATA INFILE command which is used to import data to MySQL. When LOCAL is specified, data files can be located on the client host. \\ If No is specified, the LOCAL keyword is not generated and data files must be located on the server before importing. \\ Possible values - Yes, No. The default value is Yes. | +| **IMPORT_FROM_CLIENT** | If Yes is specified, the LOCAL keyword is generated for MySQL LOAD DATA INFILE command which is used to import data to MySQL. When LOCAL is specified, data files can be located on the client host. \\ If No is specified, the LOCAL keyword is not generated and data files must be located on the server before import. \\ Possible values - Yes, No. The default value is Yes. | 
-| **DATA_LOAD_OPTION** | If Replace is specified, existing rows are updated in an existing table based on primary or unique key information or added to the table if a primary key is not matched. If Ignore is specified, existing rows in the table are not updated, when primary or unique key values are equivalent to existing values in the table. The rows from the text file which do not match primary or unique key in the table are inserted. | +| **DATA_LOAD_OPTION** | If Replace is specified, existing rows will be updated in an existing table based on primary or unique key information or added to the table if a primary key is not matched. If Ignore is specified, existing rows in the table will not be updated, when primary or unique key values are equivalent to existing values in the table. The rows from the text file which do not match primary or unique key in the table are inserted. | 
-| **ENABLE_PARTITIONING** | This option was added for Oracle to MySQL conversion. If it is Yes, all the columns from partition clause which are not in primary key are added to primary key definition. If it is No or not specified, all partition clauses are removed from a MySQL equivalent. Possible values are Yes, No. The default is No. | +| **ENABLE_PARTITIONING** | This option was added for Oracle to MySQL conversion. If it is set to Yes, all the columns from partition clause which are not in primary key will be added to primary key definition. If it is set to No or not specified, all partition clauses will be removed from a MySQL equivalent. Possible values are Yes, No. The default value is No. | 
-| **EXISTS2JOIN** | If it is Yes, all the occurrences of EXISTS clauses in SELECT statements are replaced with the tables placed to common FROM clause and conditions placed to common WHERE clause. Possible values - Yes, No. The default is No. | +| **EXISTS2JOIN** | If it is set to Yes, all the occurrences of EXISTS clauses in SELECT statements will be replaced by the tables placed to common FROM clause and conditions placed to common WHERE clause. Possible values - Yes, No. The default value is No. | 
-| **IN2JOIN** | If this option is Yes, all the occurrences of IN clauses in WHERE condition are moved to JOIN conditions with ON clause. Possible values - Yes, No. The default is No. | +| **IN2JOIN** | If this option is set to Yes, all the occurrences of IN clauses in WHERE condition will be moved to JOIN conditions with ON clause. Possible values - Yes, No. The default value is No. | 
-| **FOREIGN_KEY_CHECKS** | This option was added to ignore foreign key constraints during LOAD DATA operation and ignore check of data when adding FOREIGN KEY constraints to the table. Possible values - Yes, No. The default is No. |+| **FOREIGN_KEY_CHECKS** | This option was added to ignore foreign key constraints during LOAD DATA operation and to ignore check of data when adding FOREIGN KEY constraints to the table. Possible values - Yes, No. The default value is No. |
 | **CONVERT_PARTITIONS** | This option allows to convert RANGE and LIST partitions for Oracle to MySQL conversion direction. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | | **CONVERT_PARTITIONS** | This option allows to convert RANGE and LIST partitions for Oracle to MySQL conversion direction. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. |
 | **CHARACTER_SET** | This option defines the encoding that will be used to store the extracted data in the files in export folder. | | **CHARACTER_SET** | This option defines the encoding that will be used to store the extracted data in the files in export folder. |
Line 27: Line 27:
 | **KEY_LENGTH_FOR_BLOB_IDX** | If MySQL index is created on BLOB/TEXT columns, key length value should be specified for such columns. So this option defines the key length value for BLOB/TEXT columns that are used in indexes. \\ Possible values - number from 0 and higher. \\ Default value - 255. |ENABLE_LOCAL_LOAD | **KEY_LENGTH_FOR_BLOB_IDX** | If MySQL index is created on BLOB/TEXT columns, key length value should be specified for such columns. So this option defines the key length value for BLOB/TEXT columns that are used in indexes. \\ Possible values - number from 0 and higher. \\ Default value - 255. |ENABLE_LOCAL_LOAD
 | **ENABLE_LOCAL_LOAD** | This option controls the local data load into MySQL database. If this option is set to Yes, mysql.exe utility will be run with the local-infile option, which allows to use LOAD DATA LOCAL command in the .ldi file to load data into the target server from the local machine. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | | **ENABLE_LOCAL_LOAD** | This option controls the local data load into MySQL database. If this option is set to Yes, mysql.exe utility will be run with the local-infile option, which allows to use LOAD DATA LOCAL command in the .ldi file to load data into the target server from the local machine. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". |
 +| **CREATE_DEFINER** | This option controls whether the definer clause should be added to the procedures, functions and triggers when migrating into MySQL database. In this option we need to specify a user that will be used in CREATE DEFINER clause in generated MySQL code. If this option is set to "No" or empty, CREATE DEFINER clause will not be added to the MySQL objects.\\ Default value - "No" or Empty. |
 +| **PRESERVE_COMMENTS** | This option controls whether the comments inside the sql should be saved during the import process. If this option is set to "Yes", SQLWays will generate command to mysql.exe utility with the option ”–comments”. And mysql.exe utility will save the comments inside the sql code during the import. If this option is set to "No", SQLWays will use ”–skip comments” option with mysql.exe utility. And this utility will not save comments inside the SQL code during the import.\\ Possible values - "Yes" or "No". \\ Default value - "No" or Empty. |
 +| **CREATE_CONDITION_HANDLER** | This option was created to emulate the Transact-SQL behavior inside MySQL stored procedures and functions when the error in one of the statements inside the procedure or function body arises. By default this option is set to "Yes". And SQLWays adds the CONDITION HANDLER to each “BEGIN…END” block that handles the error arose without terminating the procedure or function execution. The errors are hidden in the case. When this option is set to "No", no CONDITION HANDLER is added and the first error encountered during the procedure or function run terminates the procedure or function execution. The error message will be returned after the procedure terminates. \\ Possible values - "Yes" or "No". \\ Default value - "Yes". |
 +| **USE_FN_CHARACTERISTIC** | This option defines whether the characteristic block will be generated for MySQL functions. \\ Possible values - "Yes" or "No" or Empty. \\ Default value - "No" or Empty. |
 +| **BIT_DATATYPE** | This option defines how to convert BIT data types into MySQL database. \\ Default value - CHAR(1). |
  
 **Example**: **Example**:
sqlways/command-line/sqlways-ini/mysql-section.1536325974.txt.gz · Last modified: September 07, 2018, 01:12:54 PM by alexandr.kirpichny
 
© 1999-2018, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement