Define columns of a relational table - ApsaraDB for OceanBase

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

Syntax

relational_properties:
{ column_definition
| virtual_column_definition
| period_definition
| { out_of_line_constraint | out_of_line_ref_constraint }
| supplemental_logging_props
}
  [, { column_definition
     | virtual_column_definition
     | period_definition
     | { out_of_line_constraint | out_of_line_ref_constraint }
     | supplemental_logging_props
     }
  ]...
  
 period_definition:
 PERIOD FOR valid_time_column [ ( start_time_column, end_time_column ) ]
 
 supplemental_logging_props:
 UPPLEMENTAL LOG { supplemental_log_grp_clause | supplemental_id_key_clause}

Supported operations

Defining regular columns by using the column_definition option is supported. For more information, see Regular columns.
Defining virtual tables by using the virtual_column_definition option is supported. For more information, see Virtual columns.
Defining constraints are supported. For more information, see Constraints.

Ignored clauses and options

Note

The following clauses and options will be ignored and will not be resolved or converted when they are specified in the synchronized DDL statements.

The period_definition option for specifying the effective period.
The supplemental_logging_props option for supplemental logging.