mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
f89e6c442c
Don't fail when an frm is inconsistent (legacy DB_TYPE_xxx code doesn't match the engine name), use the engine name, ignore the legacy code.
20 lines
682 B
Text
20 lines
682 B
Text
#
|
|
# MDEV-5029 Crash in MariaDB 5.5.33 with .frm from older MariaDB release
|
|
#
|
|
# a.k.a. fail to open an frm with indexes:
|
|
|
|
let $datadir=`select @@datadir`;
|
|
|
|
# normal innodb table (but innodb is disabled here)
|
|
copy_file std_data/mdev5029_1.frm $datadir/test/t1.frm;
|
|
--error ER_UNKNOWN_STORAGE_ENGINE
|
|
show create table t1;
|
|
remove_file $datadir/test/t1.frm;
|
|
|
|
# Aria table, incorrect typecode
|
|
call mtr.add_suppression("t1.frm is inconsistent: engine typecode 43, engine name Aria");
|
|
copy_file std_data/mdev5029_2.frm $datadir/test/t1.frm;
|
|
copy_file std_data/mdev5029_2.MAI $datadir/test/t1.MAI;
|
|
copy_file std_data/mdev5029_2.MAD $datadir/test/t1.MAD;
|
|
show create table t1;
|
|
drop table t1;
|