Package Checks (CDM/LDM/PDM)

PowerDesigner provides default model checks to verify the validity of packages.

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. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - None.
Name/Code contains synonyms of glossary terms	[if glossary enabled] Names and codes must not contain synonyms of glossary terms. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - Replaces synonyms with their associated glossary terms.
Circular references	[PDM only] A circular reference occurs when a table refers to another table, and so on until a loop is created between tables. A package cannot contain circular references. Manual correction: Resolve the circular reference by correcting the reference, deleting its source, or clearing the Mandatory parent or Check on commit option Automatic correction: None
Constraint name uniqueness	[PDM only] A constraint name is a unique identifier for the constraint definition of tables, columns, primary and foreign keys in the database. You define the constraint name in the following tabs: Check tab of the table property sheet Additional Check tab of the column property sheet General tab of the key property sheet A constraint name must be unique in a model. Manual correction: Modify the duplicated constraint name in the corresponding tab Automatic correction: Modifies the duplicated constraint name of a selected object by appending a number to its current name
Constraint name maximum length	[PDM only] The constraint name length cannot be longer than the length specified in the DBMS definition: either in the MaxConstLen entry, in the Object category, or in each object category. Manual correction: Modify the constraint name to meet this requirement Automatic correction: Truncates the constraint name to the maximum length specified in the DBMS definition
Circular dependencies	[PDM only] Traceability links of type `<<DBCreateAfter>>` can be used to define a generation order for stored procedures and views. These links should not introduce circular dependencies in the model. Manual correction: Remove the link. Automatic correction: None
Circular dependency	[CDM/LDM only] A circular dependency occurs when an entity depends on another and so on until a dependency loop is created between entities. A package cannot contain circular dependencies. Manual correction: Clear the Dependent check box for the link or delete an inheritance link. Automatic correction: None.
Circularity with mandatory links	[CDM/LDM only] A circular dependency occurs when an entity depends on another and so on until a dependency loop is created between entities through mandatory links. Manual correction: Clear the Mandatory parent check box or delete a dependency on a relationship. Automatic correction: None.
Shortcut code uniqueness	Shortcuts codes must be unique in a namespace. Manual correction: Change the code of one of the shortcuts Automatic correction: None
Shortcut potentially generated as child table of a reference	[CDM/LDM only] The package should not contain associations or relationships with an external shortcut as child entity. Although this can be tolerated in the CDM, the association or relationship will not be generated in a PDM if the external shortcut is generated as a shortcut. Manual correction: Modify the design of your model in order to create the association or relationship in the package where the child entity is defined. Automatic correction: None.