diff options
| author | Alexander Barkov <bar@mariadb.com> | 2022-10-25 11:53:39 +0400 |
|---|---|---|
| committer | Alexander Barkov <bar@mariadb.com> | 2022-10-25 17:34:25 +0400 |
| commit | f1bbc1cd19d0d81fee5433efcb570a8845172241 (patch) | |
| tree | 2e5a6b7808116456b4baea44ae15f69bbe1e24e8 /mysql-test/main/join_cache.result | |
| parent | 8c5d323326d9d527e9a5e08c69eb6085953eb130 (diff) | |
| download | mariadb-git-f1bbc1cd19d0d81fee5433efcb570a8845172241.tar.gz | |
MDEV-28545 MyISAM reorganize partition corrupt older table format
The ALTER related code cannot do at the same time both:
- modify partitions
- change column data types
Explicit changing of a column data type together with a partition change is
prohibited by the parter, so this is not allowed and returns a syntax error:
ALTER TABLE t MODIFY ts BIGINT, DROP PARTITION p1;
This fix additionally disables implicit data type upgrade
(e.g. from "MariaDB 5.3 TIME" to "MySQL 5.6 TIME", or the other way
around according to the current mysql56_temporal_format) in case of
an ALTER modifying partitions, e.g.:
ALTER TABLE t DROP PARTITION p1;
In such commands now only the partition change happens, while
the data types stay unchanged.
One can additionally run:
ALTER TABLE t FORCE;
either before or after the ALTER modifying partitions to
upgrade data types according to mysql56_temporal_format.
Diffstat (limited to 'mysql-test/main/join_cache.result')
0 files changed, 0 insertions, 0 deletions
