PowerDesigner provides default model checks to verify the validity of packages.
Check |
Description and Correction |
---|---|
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.
|
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:
A constraint name must be unique in a model.
|
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.
|
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.
|
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.
|
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.
|
Shortcut code uniqueness |
Shortcuts codes must be unique in a namespace.
|
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.
|