mariadb/mysql-test/suite/versioning
Aleksey Midenkov 139117528a MDEV-22153 ALTER add default history partitions makes table inaccessible
ADD default history partitions generates wrong partition name,
f.ex. p2 instead of p1. Gap in sequence of partition names leads to
ha_partition::open_read_partitions() fail on inexistent name.

Manual fixing such broken table requires:

1. create empty table by any name (t_empty) with correct number
of partitions;
2. stop the server;
3. rename data files (.myd, .myi or .ibd) of broken table to t_empty
fixing the partition sequence (#p2 to #p1, #p3 to #p2);
4. start the server;
5. drop the broken table;
6. rename t_empty to correct table name.
2020-04-06 06:26:46 +03:00
..
r MDEV-22153 ALTER add default history partitions makes table inaccessible 2020-04-06 06:26:46 +03:00
t MDEV-22153 ALTER add default history partitions makes table inaccessible 2020-04-06 06:26:46 +03:00
common.inc versioning test suite fixes 2019-10-10 00:20:34 +03:00
common.opt Tests: versioning suite fix when no test_versioning plugin 2019-07-09 10:01:54 +03:00
common_finish.inc versioning test suite fixes 2019-10-10 00:20:34 +03:00
disabled.def MDEV-14820 System versioning is applied incorrectly to CTEs 2018-05-12 10:16:45 +02:00
engines.combinations MDEV-15458 Segfault in heap_scan() upon UPDATE after ADD SYSTEM VERSIONING 2019-05-17 13:53:22 +02:00
engines.inc versioning/common.inc must "have_innodb" 2017-12-05 17:42:27 +03:00
innodb.combinations MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING 2018-11-01 16:42:06 +02:00
innodb.inc MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING 2018-11-01 16:42:06 +02:00
key_type.combinations versioning test suite fixes 2019-10-10 00:20:34 +03:00
key_type.inc versioning test suite fixes 2019-10-10 00:20:34 +03:00
wait_system_clock.inc fix tests on windows 2018-01-13 02:01:35 +01:00