2010-07-08 14:36:55 +02:00
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
|
#
|
|
|
|
|
# Bug#46086: crash when dropping a partitioned table and
|
|
|
|
|
# the original engine is disabled
|
|
|
|
|
# Copy a .frm and .par file which was created with:
|
|
|
|
|
# create table `t1` (`id` int primary key) engine=blackhole
|
|
|
|
|
# partition by key () partitions 1;
|
|
|
|
|
SHOW TABLES;
|
|
|
|
|
Tables_in_test
|
|
|
|
|
t1
|
|
|
|
|
SHOW CREATE TABLE t1;
|
MDEV-27753 Incorrect ENGINE type of table after crash for CONNECT table
whenever possible, partitioning should use the full
partition plugin name, not the one byte legacy code.
Normally, ha_partition can get the engine plugin from
table_share->default_part_plugin.
But in some cases, e.g. in DROP TABLE, the table isn't
opened, table_share is NULL, and ha_partition has to parse
the frm, much like dd_frm_type() does.
temporary_tables.cc, sql_table.cc:
When dropping a table, it must be deleted in the engine
first, then frm file. Because frm can be the only true
source of metadata that the engine might need for DROP.
table.cc:
when opening a partitioned table, if the engine for
partitions is not found, do not fallback to MyISAM.
2022-03-11 20:18:22 +01:00
|
|
|
ERROR HY000: Incorrect information in file: './test/t1.frm'
|
2010-07-08 14:36:55 +02:00
|
|
|
DROP TABLE t1;
|
2015-06-16 17:27:53 +02:00
|
|
|
ERROR HY000: Got error 1 "Operation not permitted" from storage engine partition
|
2010-07-08 14:36:55 +02:00
|
|
|
t1.frm
|
|
|
|
|
t1.par
|
