All Products
Search
Document Center

ApsaraDB for OceanBase:Inline constraints

Last Updated:Jun 03, 2024

This topic describes the conversion scope of CREATE TABLE DDL operations for inline constraints during data migration from an Oracle database to an Oracle tenant of OceanBase Database.

Syntax

The syntax of inline_constraint is as follows:

[ CONSTRAINT constraint_name ]
{ [ NOT ] NULL
| UNIQUE
| PRIMARY KEY
| references_clause
| CHECK (condition)
}
[ constraint_state ]

references_clause:
REFERENCES [ schema_name. ] object [ (column [, column ]...) ]
  [ON DELETE { CASCADE | SET NULL } ]

constraint_state:
[ [NOT] DEFERRABLE [INITIALLY {IMMEDIATE | DEFERRED}]
 |  INITIALLY { IMMEDIATE | DEFERRED } [ NOT ] [ DEFERRABLE ]
]
[  RELY | NORELY  ]
[ using_index_clause ]
[ ENABLE | DISABLE ]
[ VALIDATE | NOVALIDATE ]
[ exceptions_clause ]

Supported DDL

  • Defining constraint names by using the CONSTRAINT constraint_name clause is supported.

  • Specifying the NULL or NOT NULL attribute is supported.

  • Specifying the UNIQUE and PRIMARY KEY constraints is supported.

Unsupported DDL

  • CHECK is not supported. If this option is used, it is ignored.

  • Defining the foreign key by using the references_clause clause is not supported. If this clause is used, it is ignored.

  • Specifying the constraint state by using the constraint_state option is not supported. If this option is used, it is ignored.