PowerDesigner provides default model checks to verify the validity of tables.
Check |
Description and Correction |
---|---|
Table name and code uniqueness |
Tables 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 |
Table name and code length |
The table name and code length is limited by the maximum length specified in the DBMS definition (MaxLen entry, in the category) and in the naming conventions of the model options.Manual correction: Modify the name/code length to meet this requirement Automatic correction: Truncates the name/code length to the maximum length specified in the DBMS definition |
Constraint name conflict with index name |
A constraint name of the table cannot be the same as an index name. Manual correction: Change the name of the table constraint Automatic correction: None |
Existence of column, reference, index, key |
A table should contain at least one column, one index, one key, and one reference. Manual correction: Add missing item to the definition of the table Automatic correction: None |
Number of auto-incremented columns |
Auto-incremented columns contain automatically calculated values. A table cannot contain more than one auto-incremented column. Manual correction: Delete all but one auto-incremented column Automatic correction: None |
Table index definition uniqueness |
Identical indexes are indexes with the same columns, order and type. A table cannot have identical indexes. Manual correction: Delete index or change its properties Automatic correction: None |
Table mapping not defined |
When a table belongs to a model containing one or several data sources, it must be mapped to tables or views in the data source in order to establish a relational to relational mapping. Manual correction: Map the current table to one or several tables or views in the model belonging to the data source Automatic correction: Destroys the mapping for the table. This removes the data source from the Mapping list in the table Mapping tab |
Column mapping not defined |
When a column belong to a table in a model containing one or several data sources, it should be mapped to columns in the data source in order to establish a relational to relational mapping. Manual correction: Map the current column to one or several columns in the models belonging to the data source Automatic correction: Destroys the mapping for the column. This removes the columns that are not mapped to any object in the Columns Mapping tab of the table Mapping tab |
Existence of permission |
Permissions are usage restrictions set on a table for a particular user, group or role. Manual correction: Define permissions on the table for users, groups and roles Automatic correction: None |