Configuring SQL Designer

Overview of component configuration

Objecteering SQL Designer can be parameterized to meet your specific needs. This parameterization is carried out in the "Modifying configuration" dialog box, which is launched either by clicking on the
"Modify MDAC configuration" button, or through the "Tools/MDACs options" menu.

Parameter sets

In the SQL parameter category, five different sets of parameters are available:

· General

· Physical generation

· Diagram generation on physical model

· SQL generation

· SQL generation filters

The "General" parameter set

Figure 2. The "General" parameter set

Configuration options are identical for Oracle, Sybase and SQL Server.

The ... option	is used to ...
Database		specify the target RDBMS.

The "Physical generation" parameter set

Figure 3. The "Physical generation" parameter set

The ... option	is used to ...
Generate compositions		activate specific generation of compositions. If deactivated, compositions are handled as simple associations.
Show associations in the physical model		display associations in the physical model.
Default class attributes specific table name		determine the class attribute table name for each class which has attributes which are not annotated {globalTag}. %tableName% is replaced by the table name generated from the class.
Default string column size		determine the size of string columns where the "Type constraint/String size" has not been defined on the source attribute (only for databases that do not manage empty columns).
Default char column size		determine the size of Char-type columns when the "Max" property has not been defined on the source attribute (only for databases that do not manage empty columns).
Generates filter column on tables generated with "one table" pattern		generate a filter column on tables generated using the "one table" pattern.
SQL upper case		generate in upper case. This feature allows you to select the generation of all relational unit names in capital letters. If none is specified, the symbols correspond to those entered in Objecteering.
Generate class-association table name from the association name		indicate that the name of the table generated from a class association is the name of the association. If the tickbox is not checked, the name of the table generated from a class association is the name of the class association.
Display char/string size warning		display or not display warnings in the report box, when the size of char or string-type attributes has not been entered.
Using SQL Types package in MPD		generate a types package in the physical model containing the SQL types used in the logical model. Attributes annotated using the {sqlType} tagged value will then be typed with the types featuring in this types package.

The "Diagram generation on physical model" parameter set

Figure 4. The "Diagram generation on physical model" parameter set

The ... option	is used to ...
Generate diagram with physical model		automatically generate a class diagram on the physical model.
Show tagged values in diagram		display tagged values in the physical model class diagram.
Color keys in diagram		color attributes in the generated diagram to highlight primary and foreign keys.
Primary key color		determine the color of the primary key attribute. The color must have "red, green, blue" syntax, where red, green and blue are numbers included between 0 (for black) and 255 (full red, green and blue).
Foreign key color		determine the color of the foreign key attribute. The color must have "red, green, blue" syntax, where red, green and blue are numbers included between 0 (for black) and 255 (full red, green and blue).
Foreign primary key color		determine the color of the foreign primary key attribute. The color must have "red, green, blue" syntax, where red, green and blue are numbers included between 0 (for black) and 255 (full red, green and blue).
Element font		determine the font used in the diagram. Use the "Resources" button in the tool box and customize one of the element fonts, and then copy and paste the "font" field from the "Resources" dialog box to the MDAC parameter.

The "SQL generation" parameter set

Figure 5. The "SQL generation" parameter set

The ... option	is used to ...
Default generation path		specify the directory for the generation of SQL files.
Default SQL files suffix		specify the default suffix used for SQL files.
User custom types package name		specify the user customized type mapping project name. This parameter is optional and is left undefined by default.
Maximum String size		parameterize the maximum size of String-type columns. When the parameter has not been defined, the maximum size by default is 255.
Maximum Char size		parameterize the maximum size of char-type columns. When the parameter has not been defined, the maximum size by default is 255.
Database user		indicate the name of the user of the database.
Database user password		indicate the password for the database user indicated.
Custom SQL interpreter		indicate the name and the path of the SQL interpreter.
Custom server		indicate the name and the path of the server.

SQL generation filters

Figure 6. The "SQL generation filters" parameter set

The ... option	is used to ...
Creation file	generate a creation file. This feature allows the generation of creation orders corresponding to the model's mapping.
Destruction file	generate a deletion file. This feature allows the generation of deletion orders corresponding to the model's mapping.
Keep old deletion file	keep a backup of the old delete file before each generation. It can be executed to cancel the old creation file.
Execute old deletion file before creation file	execute the backup delete file before the new creation file, which cancels the old creation file effect.
User SQL code	take into account the user SQL code.
Objecteering comments	take into account Objecteering comments. This is used to generate comments built by Objecteering, in order to provide improved legibility of the SQL source produced.
Commit	generate "commit" orders. This generates a "commit" after each creation (or deletion) batch, in order to allow the RDBMS to record orders, without waiting for the interpretation of all the SQL orders to be completed.
Primary key	generate the primary key associated to the tables corresponding to the operation's model, if they are present.
Indexes and other keys	take into account secondary keys and indexes. This feature is used to generate the secondary keys and indexes associated to the tables corresponding to the operation's model, if they are present.
Integrity constraints	generate constraints deduced from associations. This feature selects those integrity constraints associated with the operation's units, if they are present.
Triggers	generate triggers.