Database Package Checks (PDM)

PowerDesigner provides default model checks to verify the validity of database 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.
Name/Code uniqueness	Object names must be unique in the namespace. Manual correction - Modify the duplicate name or code. Automatic correction - Appends a number to the duplicate name or 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 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 (at Objects > DB Package > MaxLen)
Existence of package `sub-object`	A database package must have a number of sub-objects defined in order to be correctly modeled. Manual correction: Create one or more of the relevant object on the appropriate tab of the database package property sheet: Procedures (or use existing stored procedures and duplicate them in the database package) Cursors Variables Types Exceptions Automatic correction: None