You can use special functions to influence export of DDL files with special targets.
Overview of Special Functions
You can use both your own oAW workflows in the respective XML configuration files and your own special functions to individually customize your processes when exporting DDL files you wish to describe, modify or remove data structures for.
The following special functions can be used for this.
-
Arguments Not Included by Default
-
Options for your Own DDLs
Using Database Standard Options in Innovator
The $INODIR\java\InoIMInOut\configuration directory contains the standardOptions.xml template file. This can be used during DDL generation under $INODIR\java\Innovator.codegen\configuration\de\mid\data\ by activating the hidden Standard DDL Options section.
You can either use the standardOptions.xml standard options file or your own file; this then needs to be entered in the aforementioned section for the standardDDLOptionsFileName argument.
Explicitly set Innovator type system values overwrite the standard options in standardOptions.xml or your own file.
Options defined in the respective standard options file are always generated with the <gen>yes</gen> tag; even if the Innovator type system option default is the same as this value. Options defined with the <gen>no</gen> tag are only generated if an explicit value is set in the model.
The target uses the entry to set the order of the options in the DDL. Options entered in the standard options file are generated first. Options not entered in the file but which have an explicit value in the model are added afterwards.
Arguments Not Included by Default
Comments of Tables and Columns with ER Names for Linked Entities and Attributes
The Generate comments for conceptual names option in the Comments group affects how comments with the name of the conceptual objects (entities and attributes) that are linked with tables and columns are outputted in the DDL configuration.
Prefix "SET SCHEMA <SchemaName>;"
If you set the -p setSchema=true argument for a DDL generation, then a row SET SCHEMA <SchemaName>; prefixes the DDL result. The <SchemaName> value applies to the owner of the object first selected which was called for DDL generation.
Loading Existing Tables with New Structure for AlterTable DDL Generation
The reloadTables=true call argument implements a new structuring of existing tables.
Sorting Multiple Schemata
DDL generation in various schema only sorts according to DB object name with the -p collectByTableNamesOnly=true argument (default is false). Even if the schema name is not outputted in the DDL, sorting occurs first according to schemata name and then according to DB objects name by default.
Sequences and Sequence Data Types
Table columns can be used directly as sequences - similar to DDL generation for sequence data types. A stereotype property of the Enumeration type with the GenerationType name and the DEFAULT and ALWAYS values must exist for a table column.
The existing stereotype properties StartValue, Increment, Minimum, Maximum and Cache of the String type and the stereotype properties CycleOption and OrderOption of the Boolean Term type are evaluated to initiate the correct inline generation for the column.
All given names and values are logical names and values in the configuration.
