Chapter 9 Working with PDMs


Package checks

The following PDM model checks are made on packages:

Check Description and Correction
Circular references 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.

Manual correction: Resolve the circular reference by correcting the reference, deleting its source, or clearing the Mandatory parent or Check on commit option

Automatic correction: None
Constraint name uniqueness 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:

Check tab of the table property sheet

Additional Check tab of the column property sheet

General tab of the key property sheet

A constraint name must be unique in a model.

Manual correction: Modify the duplicated constraint name in the corresponding tab

Automatic correction: Modifies the duplicated constraint name of a selected object by appending a number to its current name
Constraint name maximum length 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.

Manual correction: Modify the constraint name to meet this requirement

Automatic correction: Truncates the constraint name to the maximum length specified in the DBMS definition
Circular dependencies Extended dependencies with the stereotype <<DBCreateAfter>> can be used between stored procedures to define a generation order for stored procedures. An extended dependency with the stereotype <<DBCreateAfter>> should not introduce a circular dependency in the model.

Manual correction: Remove the <<DBCreateAfter>> extended dependency

Automatic correction: None
Shortcut code uniqueness Shortcuts codes must be unique in a namespace.

Manual correction: Change the code of one of the shortcuts

Automatic correction: None

 


Copyright (C) 2007. Sybase Inc. All rights reserved.