PowerDesigner provides default model checks to verify the validity of columns.
Check |
Description and Correction |
---|---|
Name/Code contains terms not in glossary |
[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary.
|
Name/Code contains synonyms of glossary terms |
[if glossary enabled] Names and codes must not contain synonyms of glossary terms.
|
Name/Code uniqueness |
Object names must be unique in the namespace.
|
Column code maximum length |
The column code length is limited by the maximum length specified in the DBMS definition (MaxLen entry, in the
category) or in the naming conventions of the model options.
|
Domain divergence |
Divergence is verified between columns, domains, and data types. Various checks and attributes are also examined. One or more of the Enforce non divergence model options must be selected.
|
Column mandatory |
In some DBMS, the columns included in a key or a unique index should be mandatory.
|
Detect inconsistencies between check parameters |
The values entered in the check parameters tab are inconsistent for numeric and string data types: default does not respect minimum and maximum values, or default does not belong to list of values, or values in list are not included in minimum and maximum values, or minimum is greater than maximum value. Check parameters must be defined consistently.
|
Precision > Maximum length |
The data type precision should not be greater than the length. Note that some DBMS accept a precision higher than the length.
|
Undefined data type |
A model should not contain columns with undefined data type, all columns should have a defined data type.
|
Foreign key column data type and constraint parameters divergence |
Primary/alternate and foreign key columns involved in a join should have consistent data types and constraint parameters.
|
Column with sequence not in a key |
Since a sequence is used to initialize a key, it should be attached to a column that is part of a key. This applies to those DBMS that support sequences.
|
Auto-incremented column with data type not numeric |
An auto-incremented column must have a numeric data type.
|
Auto-incremented column is foreign key |
A foreign key column should not be auto-incremented.
|
Missing computed column expression |
A computed column should have a computed expression defined.
|
Invalid mapping from source column |
A column in a table managed by a lifecycle policy in which the first phase is associated with an external database must not be mapped to more than one column in the corresponding table in the external database.
|
Data type compatibility of mapped columns |
A column in a table managed by a lifecycle policy in which the first phase is associated with an external database must be mapped to a column with the same data type in the corresponding table in the external database.
|
Existence of mapping for mandatory columns |
A mandatory column in a table managed by a lifecycle policy in which the first phase is associated with an external database must be mapped to a column in the corresponding table in the external database.
|