[MDEV-33287] Table partitioning with only default partition bypasses data type limitations Created: 2024-01-21 Updated: 2024-01-21 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Partitioning |
| Affects Version/s: | 10.4, 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3, 11.4 |
| Fix Version/s: | 10.4, 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Alexey Botchkov |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | upstream | ||
| Description |
|
PARTITION BY LIST [COLUMNS] and PARTITION BY RANGE [COLUMNS] are limited to certain data types by design, for example, they don't support TIMESTAMP:
However, if only the default partition is defined, the operation succeeds:
Same for DEFAULT partition in PARTITION BY LIST COLUMNS. It causes confusing errors afterwards, for example upon an attempt to reorganize the partition:
Maybe there can be other unexpected effects which aren't obvious right away. If the reason is that a partitioned table with only default partition is the same as a non-partitioned table, then this should also work, but it doesn't:
and in any case it is not true, it still counts as a partitioned table, with all their limitations etc. |