PowerDesigner provides default model checks to verify the validity of abstract data type procedures.
|
Check |
Description and Correction |
|---|---|
|
Abstract data type procedure name and code uniqueness |
Abstract data type procedure names and codes must be unique in the abstract data type. Manual correction: Modify the duplicate name/code Automatic correction: Appends a number to the duplicate name/code |
|
Abstract Data Type procedure code maximum length |
The code of the ADT procedure is longer than the maximum allowed by the DBMS. Manual correction: Reduce the length of the code Automatic correction: Reduces the code to a permissible length |
|
Procedure cannot have the same name as an attribute |
An abstract data type procedure cannot have the same name as an attribute. Manual correction: Change the name of the ADT procedure Automatic correction: None |
|
Abstract data type procedure definition empty |
An abstract data type procedure must have a definition. Manual correction: Create an ADT procedure definition in the Definition tab of the ADT procedure property sheet Automatic correction: None |
|
Inconsistent return type |
If the abstract data type procedure is a function, a map or an order, you should define a return data type for the function, map or order. Manual correction: Select a return data type in the Return data type list Automatic correction: None |