Oracle Designer Model, Release 6i
Uniqueness Criteria

TRANSITION

Uniqueness may be enforced by database constraints and/or the API, depending on the complexity of the uniqueness criteria

• Database constraints are used when the uniqueness criteria can be expressed simply as a combination of columns. These are defined as unique key constraints placed on the underlying table.
• The API is used when the uniqueness criteria cannot be expressed simply as a combination of columns. These are defined in PL/SQL.

Uniqueness enforced by database constraints

The following unique key constraints exist for the underlying table SDD_TRA

Unique Key Constraint	Column
UK_TRA	( 1 ) SOURCE_ACTIVITY_REF ( 2 ) SOURCE_ACT_USAGE_REF ( 3 ) SOURCE_OBJECT_STATE_REF ( 4 ) SOURCE_PSEUDOSTATE_REF ( 5 ) SOURCE_EVENT_REF ( 6 ) TARGET_ACTIVITY_REF ( 7 ) TARGET_ACT_USAGE_REF ( 8 ) TARGET_OBJECT_STATE_REF ( 9 ) TARGET_PSEUDOSTATE_REF ( 10 ) TARGET_EVENT_REF ( 11 ) SEQUENCE_NUMBER

Uniqueness enforced in PL/SQL by the API

See API Spec for TRANSITION