This page presents the general information pertaining to databases or to the environment level LDM.
Database
Data entry
Schema (SQL bases)
Name of schema used when PDM is generated for the PC SQL database (DB2 Windows, Oracle 7 or SQL Server), for public objects.
This name is also used by the Visual or Web generators to qualify the PC SQL table, when generating Adelia SQL instructions.
The checkbox located below this field enables you to complete input:
Extended syntax |
Lets you enter a schema name that does not observe the Adelia naming conventions (upper/lower case, spaces, special characters, etc.). It is selected and grayed out if the schema does not effectively observe these conventions. By default: box not checked. |
SQL properties name
Adelia value which will be used when generating the names of SQL tables and SQL columns (AS/400 and PC).
Possible values:
Mixed |
For an SQL AS/400 PDM: short name. |
|
For a PC PDM (DB2 Windows, Oracle 7 or SQL Server): Guide word (or alternative SQL names). |
Short name |
The real name of the table will be the physical file name of the logical entity. |
|
The real name of the access will be name of the access file. |
|
The names of the SQL columns will be the short names of the logical properties. |
Guide word |
The real name of the table will be the Adelia name of the logical entity (or its alternative SQL names). |
|
The real name of the access will be the Adelia name of the access. |
|
The names of the SQL columns will be the guide words (or alternative SQL names) of the logical properties. |
SQL constraint
SQL constraint associated by default to the columns of the generated SQL tables.
Possible values:
NULL |
The column accepts the "NULL" value. It is this value which will be used if you insert a line in the table, without specifying a value for this column. |
NOT NULL |
The column does not accept the "NULL" value. It is not possible to insert a line in the table without specifying a value for this column. |
NOT NULL WITH DEFAULT |
The column does not accept the "NULL" value. It is the type default value which will be used if you insert a line in the table, without specifying a value for this column. |
NULL WITH DEFAULT |
The column accepts the "NULL" value. However, it is the type default value which will be used if you insert a line in the table, without specifying a value for this column. |
Guide word length limit
Value between 1 and 128.
This is the limit used when entering the guide word for a logical property. When the length of a guide word is greater than this limit, a warning message is sent.
The default value is 30.
Check boxes
Non variable alphanumerical in CHAR
Checked |
The non variable alphanumerical logical properties are generated in CHAR format for PC SQL DBMSs. Only alpha type variable logical properties are generated in VARCHAR format. |
Not checked |
Non variable alphanumerical logical properties are generated in VARCHAR format for PC SQL DBMSs. |
Note: For AS/400 generation, non variable alpha type logical properties are always generated in CHAR format, and variable alpha type logical properties are always generated in VARCHAR format.
Generate the primary keys as a named constraint
Checked |
SQL table primary keys are generated as PRIMARY KEY-type named constraints and have the name of the associated logic file. |
Not checked |
SQL table primary keys are classically generated (PRIMARY KEY option of the CREATE TABLE instruction). |
LDM generation
Check boxes
Version 6.0 or later
If this box is checked, the generation method used for the LDM will be the one of Adelia Conception for AS/400 (version 6.0), i.e.: for a hierarchical dependency relationship, the key of the CDM-highest entity will be in the first position of the resulting LDM key.
Click here to display a diagram.
Extended hierarchical dependency
If this box is checked, the hierarchical dependency is extended to the properties which are not part of the ID. When a property is to be added in a logical entity by a relationship, hierarchical dependency check is not restricted to ID properties but can cover all the properties that have been added to an entity.
Data entry
Specific DLL
Path and name of specific DLL containing specific functions used mainly during LDM generation to encode the names of the following elements:
physical and logical files,
formats,
redundant properties,
file fields,
related fields,
guide words.
If no path is specified, the DLL should be found in the Adelia Studio installation directory.
By default, the specific DLL is USERLIB128.DLL, and is located in the installation directory.
The "…" button located to the right of this field opens a Windows system dialog box that lets you select a DLL accessible from the workstation.
Click on the following links for more information on customizing specific functions and associating a specific DLL with an environment.
Suggested constraints
This section is used to specify the default values for the integrity constraints automatically suggested from the CDM.
Data entry
Deletion rule
Update rule
These options are used to define the default values of the ON DELETE and ON UPDATE triggers according to the type of relationship having served as the basis for the suggestion.
Four different types of relation are used to generate integrity constraints:
ST/App |
"Subtype" or "Dependency" relationship, and "X,Y-0,1" relationships where the mean cardinality is "0". |
XY, 11 |
Relationships including the "0N, 11", "1N,11", "01,11" and "11,11" cardinalities. |
XY, 11 |
Relationships including the "0N, 01", "1N,01", "01,01" et "11,01" cardinalities. |
N-aires |
Relationships including the "0N, 0N", "0N,1N" et "1N,1N" cardinalities. |
The possible deletion rule values are as follows:
NO ACTION |
The record is not deleted from the parent table if there is a record with the same key value in the dependent table. |
RESTRICT |
The record is not deleted from the parent table if there is a record with the same key value in the dependent table, but an immediate check is made to prevent any other constraints (or triggers) being activated in the event of an integrity violation. |
CASCADE |
When a record in the parent table is deleted, any records with the same key value in the dependent table are also deleted. |
SET NULL |
When a record in the parent table is deleted, any records with the same key value in the dependent table are also updated. All the "key" fields in any such records that can take a "null" value are updated with the null value. |
SET DEFAULT |
When a record in the parent table is deleted, any records with the same key value in the dependent table are also updated. All the "key" fields in any such records are updated with the column's default value. |
None |
No integrity constraints will be applied to the relation type concerned. |
The deletion rule values by default are as follows:
ST/App |
CASCADE |
XY, 11 |
RESTRICT |
XY, 11 |
SET DEFAULT |
N-aires |
RESTRICT |
Note: if "None" is specified as a deletion and/or update rule for a given relationship type, no constraints are suggested for the entities resulting from this type of relationship.
The possible update rule values are as follows:
NO ACTION |
The parent table is not updated if there is a record with the same key value in the dependent table. |
RESTRICT |
The parent table is not updated if there is a record with the same key value in the dependent table, but an immediate check is made to prevent any other constraints (or triggers) being activated in the event of an integrity violation. |
CASCADE |
When a record in the parent table is updated, any records with the same key value in the dependent table is also updated. All the "key" fields in any such records are updated with the new value of the corresponding key from the parent table. |
SET NULL |
When a record in the parent table is updated, any records with the same key value in the dependent table is also updated. All the "key" fields in any such records that can take a "null" value are updated with the null value. |
SET DEFAULT |
When a record in the parent table is updated, any records with the same key value in the dependent table is also updated. All the "key" fields in any such records are updated with the column's default value. |
None |
No integrity constraints will be applied to the relation type concerned. |
The update rule values by default are as follows:
ST/App |
RESTRICT |
XY, 11 |
RESTRICT |
XY, 11 |
RESTRICT |
N-aires |
RESTRICT |
Note: if "None" is specified as a deletion and/or update rule for a given relationship type, no constraints are suggested for the entities resulting from this type of relationship.
Check boxes
Suggest corresponding uniqueness constraints
When the suggestion module creates a foreign key constraint, this module automatically creates a unique key constraint in the parent entity if it does not already exist.
Suggest check constraints
The suggestion module automatically creates check type constraints from the logical properties of these latter define a value list or interval.
Buttons
Undo
This button cancels the modifications made and restores the application to its previous state.
Default
This button cancels the modifications made and restores the application to the state it had when the environment was created.
Note: A click on the icon 
situated on the upper left-hand corner of the dialog box closes the box (keyboard shortcut: Alt+F4). If modifications were made, a confirmation screen appears.