All Products
Search
Document Center

ApsaraDB for OceanBase:Overview

Last Updated:Jun 03, 2024

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

Syntax

Syntax of constraint:

{ inline_constraint
| out_of_line_constraint
| inline_ref_constraint
| out_of_line_ref_constraint
}

inline_ref_constraint:
{ SCOPE  IS [ schema_name. ] scope_table
| WITH ROWID
| [ CONSTRAINT constraint_name ]
  references_clause
  [ constraint_state ]
}

out_of_line_ref_constraint:
{ SCOPE FOR ({ ref_col | ref_attr })lob_storage_clause
    IS [ schema_name. ] scope_table
| REF ({ ref_col | ref_attr }) WITH ROWID
| [ CONSTRAINT constraint_name ] FOREIGN KEY
    ( { ref_col [, ref_col ] | ref_attr [, ref_attr ] } ) references_clause
    [ constraint_state ]
}

Supported operations

  • Defining inline constraints by using the inline_constraint clause is supported. For more information, see Inline constraints.

  • Defining out-of-line constraints by using the `out_of_line_constraint` clause is supported. For more information, see Out-of-line constraints.

Unsupported operations

  • Defining inline REF constraints by using the inline_ref_constraint option is not supported. This option will be ignored.

  • Defining out-of-line REF constraints by using the out_of_line_ref_constraint clause is not supported. This option will be ignored.