PowerDesigner provides default model checks to verify the validity of database packages.
Check |
Description and Correction |
---|---|
Database package name and code uniqueness |
Database package 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 |
Database package name and code maximum length |
The database package name and code length is limited by the maximum length specified in the DBMS definition (MaxLen entry, in the Package 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 |
Existence of package procedure |
A database package is an encapsulated collection of related procedures. It should contain at least one procedure. Manual correction: Create one or several procedures in the database package or use existing stored procedures and duplicate them in the database package Automatic correction: None |
Existence of package cursor |
This check is to suggest that a database package can contain cursors to define a work area and access its stored information. Manual correction: Create one or several cursors in the Cursors tab of the database package property sheet Automatic correction: None |
Existence of package variable |
This check is to suggest that a database package can contain variables to capture or provide a value when one is needed. Manual correction: Create one or several variables in the Variables tab of the database package property sheet Automatic correction: None |
Existence of package type |
This check is to suggest that a database package can contain user-defined data types called types. Manual correction: Create one or several types in the Types tab of the database package property sheet Automatic correction: None |
Existence of package exception |
This check is to suggest that a database package can contain exceptions to handle internal and user-defined error conditions. Manual correction: Create one or several exceptions in the Exceptions tab of the database package property sheet Automatic correction: None |