Details
-
Task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.2.2-1, 10.2.2-2
Description
Not all table partitioning has the ability to add a so called "catch all". The catch all is present in range partitioning:
partition last values less than(MAXVALUE)
The proposal is to add similar statements to list partitioning: Proposed syntax:
partition last values not in other
Benefits: No more insert exceptions, giving the DBA more choices in applying this partitioning with less effort.
Oracle uses the following syntax for this:
CREATE TABLE h2 (c1 NUMBER,c2 NUMBER)
PARTITION BY LIST(c1) (
PARTITION p0 VALUES (1, 4, 7),
PARTITION p1 VALUES (2, 5, 8),
PARTITION p3 VALUES(DEFAULT)
We should probably use the DEFAULT syntax for this.
Attachments
Issue Links
- is part of
-
MDEV-10137 Providing compatibility to other databases
- Open
- relates to
-
MDEV-10760 Faster adding PARTITIONs in the table with DEFAULT partition (ALTER TABLE ADD PARTITION)
- Open
-
MDEV-10763 Wrong result - server does not return NULL values from default list partition after ALTER table
- Closed
-
MDEV-10765 Wrong result - query does not retrieve values from default partition on a table partitioned by list columns
- Closed
-
MDEV-11681 PARTITION BY LIST COLUMNS with default partition: Assertion `part_info->num_list_values' failed in get_part_iter_for_interval_cols_via_map
- Closed
-
MDEV-12395 DROP PARTITION does not work as expected when table has DEFAULT LIST partition
- Closed
-
MDEV-22163 Adding OVERFLOW partition
- Open