Sergei Golubchik 607d8f9e97 MDEV-14081 ALTER TABLE CHANGE COLUMN Corrupts Index Leading to Crashes in 10.2 ... 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)		2017-10-18 22:15:27 +02:00
..
btr
buf
data
dict
eval
fil
fsp
fts
fut
gis
ha
handler	MDEV-14081 ALTER TABLE CHANGE COLUMN Corrupts Index Leading to Crashes in 10.2	2017-10-18 22:15:27 +02:00
ibuf
include	MDEV-14081 ALTER TABLE CHANGE COLUMN Corrupts Index Leading to Crashes in 10.2	2017-10-18 22:15:27 +02:00
lock
log
mach
mem
mtr
mysql-test/storage_engine
os
page
pars
que
read
rem
row	MDEV-14081 ALTER TABLE CHANGE COLUMN Corrupts Index Leading to Crashes in 10.2	2017-10-18 22:15:27 +02:00
srv
sync
trx
usr
ut
bzip2.cmake
CMakeLists.txt
compile-innodb
COPYING.Google
COPYING.Percona
innodb.cmake
lz4.cmake
lzma.cmake
lzo.cmake
plugin_exports
snappy.cmake