Altering partitioned tables without partition schema definition
- Last Updated: December 12, 2014
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Syntax to alter a table to be a partitioned table without any partition schema definition
|
Syntax to create partition policies on a partitioned table without any partition schema definition
|
Parameters
- partition_policy
- Uses the following syntax:
PARTITION BY {RANGE|LIST} column_name [ PRO_DESCRIPTION desc] [subpartition_definition,...]area_spec - partition_policy_detail
- Uses the following syntax:
PARTITION [partition_name] VALUES { <= |IN }( column_values ) [area_spec][ PRO_DESCRIPTION desc ]
Notes
- To alter a partitioned table without a partition schema definition, the table
must be empty and its indexes and LOB columns must be in the type II area. All
the indexes specified in the
USING INDEXclause are marked as local and must have common prefix keys; The rest of the indexes are marked as global. - Partition policy definitions can be also be added using the
ALTER TABLE ADD PARTITIONstatement. If a table has only a row-based default index, then the default index is removed and a new default index with partitioned columns and row IDs is created.
Examples
Altering a table to be marked as a partitioned table without any partition schema definition
|
Executing the above statement marks the Order table as a partitioned
table without any partition schema definition and the index
order_idx1 is marked as a local index.
Altering a partitioned table without any partition schema definition to be a partitioned table with partition policy definitions
The following example illustrates altering a partitioned table without any partition
schema definition to a partitioned table with partition policy definitions using the
ALTER TABLE ADD PARTITION statement:
|