ALL_CONSTRAINTS
ALL_CONSTRAINTS describes constraint definitions on tables accessible to the current user.
Related Views
-
DBA_CONSTRAINTSdescribes all constraint definitions in the database. -
USER_CONSTRAINTSdescribes constraint definitions on tables in the current user’s schema.
| Column | Datatype | NULL | Description |
|---|---|---|---|
OWNER |
VARCHAR2(128) |
Owner of the constraint definition | |
CONSTRAINT_NAME |
VARCHAR2(128) |
Name of the constraint definition If the constraint is defined in a data use case domain, this column displays a system-generated constraint name. The constraint name specified in the data use case domain is displayed in |
|
CONSTRAINT_TYPE |
VARCHAR2(1) |
Type of the constraint definition:
|
|
TABLE_NAME |
VARCHAR2(128) |
Name associated with the table (or view) with the constraint definition | |
SEARCH_CONDITION |
LONG |
Text of search condition for a check constraint. This column returns the correct value only when the row originates from the current container. | |
SEARCH_CONDITION_VC |
VARCHAR2(4000) |
Text of search condition for a check constraint. This column may truncate the search condition. | |
R_OWNER |
VARCHAR2(128) |
Owner of the table referred to in a referential constraint | |
R_CONSTRAINT_NAME |
VARCHAR2(128) |
Name of the unique constraint definition for the referenced table | |
DOMAIN_OWNER |
VARCHAR2(128) |
If the constraint is inherited from a data use case domain, the owner of the data use case domain | |
DOMAIN_NAME |
VARCHAR2(128) |
If the constraint is inherited from a data use case domain, the name of the data use case domain | |
DOMAIN_CONSTRAINT_NAME |
VARCHAR2(128) |
If the constraint is inherited from a data use case domain, the name of the constraint definition, as specified in the data use case domain | |
DELETE_RULE |
VARCHAR2(9) |
Delete rule for a referential constraint:
|
|
STATUS |
VARCHAR2(8) |
Enforcement status of the constraint:
|
|
DEFERRABLE |
VARCHAR2(14) |
Indicates whether the constraint is deferrable (DEFERRABLE) or not (NOT DEFERRABLE) |
|
DEFERRED |
VARCHAR2(9) |
Indicates whether the constraint was initially deferred (DEFERRED) or not (IMMEDIATE) |
|
VALIDATED |
VARCHAR2(13) |
When
When
|
|
GENERATED |
VARCHAR2(14) |
Indicates whether the name of the constraint is user-generated ( If the constraint is defined in a data use case domain, the value of this column is always |
|
BAD |
VARCHAR2(3) |
Indicates whether this constraint specifies a century in an ambiguous manner ( See Also: the |
|
RELY |
VARCHAR2(4) |
When When See Also: constraints in Oracle AI Database SQL Language Reference |
|
PRECHECK |
VARCHAR2(10) |
Indicates whether the constraint is a precheckable JSON constraint (PRECHECK) or not (NOPRECHECK) |
|
LAST_CHANGE |
DATE |
When the constraint was last enabled or disabled | |
INDEX_OWNER |
VARCHAR2(128) |
Name of the user owning the index | |
INDEX_NAME |
VARCHAR2(128) |
Name of the index (only shown for unique and primary-key constraints) | |
INVALID |
VARCHAR2(7) |
Indicates whether the constraint is invalid (INVALID) or not (NULL) |
|
VIEW_RELATED |
VARCHAR2(14) |
Indicates whether the constraint depends on a view (DEPEND ON VIEW) or not (NULL) |
|
ORIGIN_CON_ID |
VARCHAR2(256) |
The ID of the container where the data originates. Possible values include:
|
See Also: