Oracle Designer Model, Release 6i
Uniqueness Criteria

USE_CASE_EVENT_INPUT

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_USCEVI

Unique Key Constraint	Column
UK_USCEVI	( 1 ) USE_CASE_REF ( 2 ) EVENT_CLASSIFIER_REF

Uniqueness enforced in PL/SQL by the API

See API Spec for USE_CASE_EVENT_INPUT