PowerDesigner provides default model checks to verify the validity of domains.
|
Check |
Description and Correction |
|---|---|
|
Domain name and code uniqueness |
Domain names and codes must be unique in the model. Manual correction: Modify the duplicate name/code Automatic correction: Appends a number to the duplicate name/code |
|
Domain code maximum length |
[PDM only] The domain 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. Manual correction: Modify the domain code length to meet this requirement Automatic correction: Truncates the domain code length to the maximum length specified in the DBMS definition |
|
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. Manual correction: Modify default, minimum, maximum or list of values in the check parameters tab Automatic correction: None |
|
Precision > maximum length |
The data type precision should not be greater than the length. Manual correction: Make the data type length greater than the precision Automatic correction: None |
|
Undefined data type |
A model should not contain domains with undefined data type, all domains should have a defined data type. Manual correction: Select a data type from the domain property sheet Automatic correction: None |
|
Invalid data type |
[CDM/LDM only] Invalid data types for domains exist. To be complete, a model should have all its domain data types correctly defined. Manual correction: While tolerated, you must select valid data types for currently non-valid data types to generate the PDM. Automatic correction: None. |
|
Domain missing default object |
[PDM only] A domain cannot have a default value without being attached to a default object. Manual correction: Create a default object for the domain or use the rebuild default feature Automatic correction: Creates a default object for domain |