Using Large-Object Types in Constraints
You cannot place unique, primary-key, or referential (FOREIGN KEY) constraints on BYTE or TEXT columns. You can, however, check for NULL or non-NULL values with a check constraint.
You cannot place unique or primary-key constraints on BLOB or CLOB columns. If the constraint is on a set of columns that includes a column that stores encrypted data, HCL OneDB™ cannot enforce the constraint.
You can find detailed discussions of specific constraints in the
following sections:
| Constraint | For more information, see | For an example, see |
|---|---|---|
| CHECK | CHECK Clause | Defining Check Constraints Across Columns |
| DISTINCT | Using UNIQUE or DISTINCT Constraints | Examples of the Multiple-Column Constraint Format |
| FOREIGN KEY | Using the FOREIGN KEY Constraint | Defining Composite Primary and Foreign Keys |
| PRIMARY KEY | Using the PRIMARY KEY Constraint | Defining Composite Primary and Foreign Keys |
| UNIQUE | Using UNIQUE or DISTINCT Constraints | Examples of the Multiple-Column Constraint Format |