Oracle Designer Model, Release 6i
Uniqueness Criteria

SEQUENCE_IMPLEMENTATION

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_DOI

Unique Key Constraint	Column
UK_HANDCRAFTED_DOI	( 1 ) DATABASE_USER_REF ( 2 ) VIEW_DEFINITION_REF ( 3 ) TABLE_DEFINITION_REF ( 4 ) JAVA_MODULE_REF ( 5 ) CLUSTER_REF ( 6 ) PLSQL_MODULE_REF ( 7 ) SEQUENCE_REF ( 8 ) SNAPSHOT_DEFINITION_REF ( 10 ) QUEUE_TABLE_DEF_REF

Uniqueness enforced in PL/SQL by the API

See API Spec for SEQUENCE_IMPLEMENTATION