mirror of
https://github.com/MariaDB/server.git
synced 2025-01-30 18:41:56 +01:00
607d8f9e97
remove remnants of 10.0 bugfix, incorrectly merged into 10.2 Using col_names[i] was obviously, wrong, must've been col_names[ifield->col_no]. incorrect column name resulted in innodb having index unique_id2(id1), while the server thought it's unique_id2(id4). But col_names[ifield->col_no] is wrong too, because `table` has non-renamed columns, so the correct column name is always dict_table_get_col_name(table, ifield->col_no)
24 lines
730 B
Text
24 lines
730 B
Text
--source include/have_innodb.inc
|
|
#
|
|
# MDEV-11995 ALTER TABLE proceeds despite reporting ER_TOO_LONG_KEY error
|
|
#
|
|
set @@sql_mode=strict_trans_tables;
|
|
create table t1(a text not null) row_format=dynamic engine=innodb;
|
|
create index idx1 on t1(a(3073));
|
|
show create table t1;
|
|
drop table t1;
|
|
set @@sql_mode=default;
|
|
|
|
#
|
|
# MDEV-14081 ALTER TABLE CHANGE COLUMN Corrupts Index Leading to Crashes in 10.2
|
|
#
|
|
create table t1 (
|
|
id1 int(11) not null auto_increment,
|
|
id2 varchar(30) not null,
|
|
id3 datetime not null default current_timestamp,
|
|
primary key (id1),
|
|
unique key unique_id2 (id2)
|
|
) engine=innodb;
|
|
alter table t1 change column id2 id4 varchar(100) not null;
|
|
select * from t1 where id4 like 'a';
|
|
drop table t1;
|