mirror of
https://github.com/MariaDB/server.git
synced 2025-07-26 05:04:59 +02:00
cffbb17480
Before MySQL 4.0.18, user-specified constraint names were ignored. Starting with MySQL 4.0.18, the specified constraint name was prepended with the schema name and '/'. Now we are transforming into a format where the constraint name is prepended with the dict_table_t::name and the impossible UTF-8 sequence 0xff. Generated constraint names will be ASCII decimal numbers. On upgrade, old FOREIGN KEY constraint names will be displayed without any schema name prefix. They will be updated to the new format on DDL operations. dict_foreign_t::sql_id(): Return the SQL constraint name without any schemaname/tablename\377 or schemaname/ prefix. row_rename_table_for_mysql(), dict_table_rename_in_cache(): Simplify the logic: Just rename constraints to the new format. dict_table_get_foreign_id(): Replaces dict_table_get_highest_foreign_id(). innobase_get_foreign_key_info(): Let my_error() refer to erroneous anonymous constraints as "(null)". row_delete_constraint(): Try to drop all 3 constraint name variants. Reviewed by: Thirunarayanan Balathandayuthapani Tested by: Matthias Leich
20 lines
583 B
Text
20 lines
583 B
Text
--source include/have_innodb.inc
|
|
|
|
--echo #
|
|
--echo # Bug #20762798 FK DDL: CRASH IN DICT_FOREIGN_REMOVE_FROM_CACHE
|
|
--echo #
|
|
|
|
create table t1(a int, b int, key(a),key(b))engine=innodb;
|
|
create table t2(a int, b int, key(a),key(b))engine=innodb;
|
|
|
|
alter table t2 add constraint b foreign key (b) references t1(a);
|
|
alter table t1 add constraint b1 foreign key (b) references t2(a);
|
|
|
|
alter table t2 add constraint b1 foreign key (b) references t1(a);
|
|
|
|
alter table t2 drop foreign key b1;
|
|
alter table t2 drop foreign key b;
|
|
alter table t1 drop foreign key b1;
|
|
|
|
drop table t2;
|
|
drop table t1;
|