Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:ddl-section [February 08, 2019, 12:06:07 PM]
darya.prikhodkina
sqlways:command-line:sqlways-ini:ddl-section [February 22, 2019, 12:32:18 PM] (current)
alexandr.kirpichny
Line 22: Line 22:
 | **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is available only if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is No. | | **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is available only if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is No. |
 | **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. | | **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. |
-| **OUTSCHEMA** | Outputs schema name. | +| **OUTSCHEMA** | This option can be used only when "EMPTY_SCHEMA" option is set to "No". In this option user can specify a schema name that will be used in the generated target code, instead of original one. When this option is empty, used original schema names. \\ Empty  by default. | 
-| **EMPTY_SCHEMA** | for /EMPS option. Possible values - Yes, No. |+| **EMPTY_SCHEMA** | This option defines whether the schema names should be used in the generated target script. If it is set to "Yes" - schema names will be removed. If set to "No" - schema names will be left as in the generated target code\\ Possible values - Yes, No. |
 | **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. If no value is specified, the case of the column names is not changed and column names are used as they are provided in the source database. | | **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. If no value is specified, the case of the column names is not changed and column names are used as they are provided in the source database. |
 | **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. | | **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. |
sqlways/command-line/sqlways-ini/ddl-section.1549627567.txt.gz · Last modified: February 08, 2019, 12:06:07 PM by darya.prikhodkina
 
© 1999-2019, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement