polardbxengine/mysql-test/t/foreign_key_myisam.test

--source include/force_myisam_default.inc
--source include/have_myisam.inc

# Use MyISAM for this table since we are only interested in checking syntax.
--error ER_WRONG_FK_DEF
create table t1 (
        a int not null references t2,
        b int not null references t2 (c),
        primary key (a,b),
        foreign key (a) references t3 match full,
        foreign key (a) references t3 match partial,
        foreign key (a,b) references t3 (c,d) on delete no action
          on update no action,
        foreign key (a,b) references t3 (c,d) on update cascade,
        foreign key (a,b) references t3 (c,d) on delete set default,
        foreign key (a,b) references t3 (c,d) on update set null) engine=myisam;

# Remove the problematic FKs and try again.
create table t1 (
        a int not null,
        b int not null references t2 (c),
        primary key (a,b),
        foreign key (a,b) references t3 (c,d) on delete no action
          on update no action,
        foreign key (a,b) references t3 (c,d) on update cascade,
        foreign key (a,b) references t3 (c,d) on delete set default,
        foreign key (a,b) references t3 (c,d) on update set null) engine=myisam;

create index a on t1 (a);
create unique index b on t1 (a,b);
drop table t1;

--echo #
--echo # 5) Check how parent table in different storage engine is handled.
--echo #
--echo # We handle it in the same way as if table was missing to be compatible
--echo # with pre-8.0 versions.

--echo #
--echo # 5.a) Attempt to create table with a foreign key or to add foreign key
--echo #      to already xisting table which reference parent in different SE
--echo #      should fail in FOREIGN_KEY_CHECKS=1 mode.
CREATE TABLE bad_parent (pk INT PRIMARY KEY) ENGINE=MyISAM;
--error ER_FK_CANNOT_OPEN_PARENT
CREATE TABLE child (fk INT, FOREIGN KEY (fk) REFERENCES bad_parent(pk)) ENGINE=InnoDB;

CREATE TABLE child (fk INT) ENGINE=InnoDB;
--error ER_FK_CANNOT_OPEN_PARENT
ALTER TABLE child ADD FOREIGN KEY (fk) REFERENCES bad_parent(pk);

--echo #
--echo # 5.b) However, in FOREIGN_KEY_CHECKS=0 mode this is allowed.
--echo #      Referenced table is considered missing and existing table
--echo #      in a wrong SE is not considered as real parent.
SET FOREIGN_KEY_CHECKS = 0;
ALTER TABLE child ADD FOREIGN KEY (fk) REFERENCES bad_parent(pk);
DROP TABLE child;
CREATE TABLE child (fk INT, FOREIGN KEY (fk) REFERENCES bad_parent(pk));
SET FOREIGN_KEY_CHECKS = 1;
--echo # Bad parent can be dropped just fine even in FOREIGN_KEY_CHECKS=1 mode.
DROP TABLE bad_parent;
DROP TABLE child;

--echo #
--echo # 5.c) Attempt to change SE for table participating in foreign key
--echo #      should lead to error.
CREATE TABLE parent (pk INT PRIMARY KEY) ENGINE=InnoDB;
CREATE TABLE child (fk INT, FOREIGN KEY (fk) REFERENCES parent(pk)) ENGINE=InnoDB;
--error ER_FK_CANNOT_CHANGE_ENGINE
ALTER TABLE child ENGINE=MyISAM;
--error ER_FK_CANNOT_CHANGE_ENGINE
ALTER TABLE parent ENGINE=MyISAM;
DROP TABLES child, parent;

--echo #
--echo # 5.d) It is possible to add "parent" in wrong SE to orphan foreign key.
--echo #      However, it won't be considered as real parent.
SET FOREIGN_KEY_CHECKS = 0;
CREATE TABLE child (fk INT, FOREIGN KEY (fk) REFERENCES bad_parent(pk));
SET FOREIGN_KEY_CHECKS = 1;
CREATE TABLE bad_parent (pk INT PRIMARY KEY) ENGINE=MyISAM;
--echo # It is possible to break bad parent even in FOREIGN_KEY_CHECKS=1 mode.
ALTER TABLE bad_parent DROP COLUMN pk, ADD COLUMN i INT;
DROP TABLE bad_parent;
DROP TABLE child;

--echo #
--echo # 7) Test that we check that referencing and referenced column types are
--echo #    compatible. Such check should be performed for newly created foreign
--echo #    keys and when we change types of columns in existing foreign keys.
--echo #

--echo #
--echo # 7.d) It should be impossible to create foreign keys with incompatible
--echo #      column types by adding parent to previously orphan foreign key.
SET FOREIGN_KEY_CHECKS=0;
CREATE TABLE child (fk CHAR(10), FOREIGN KEY (fk) REFERENCES parent(pk)) ENGINE=InnoDB;
--error ER_FK_INCOMPATIBLE_COLUMNS
CREATE TABLE parent (pk INT PRIMARY KEY) ENGINE=InnoDB;
CREATE TABLE parent0 (pk INT PRIMARY KEY) ENGINE=InnoDB;
--error ER_FK_INCOMPATIBLE_COLUMNS
ALTER TABLE parent0 RENAME TO parent;
--error ER_FK_INCOMPATIBLE_COLUMNS
ALTER TABLE parent0 RENAME TO parent, ADD COLUMN j INT;
--error ER_FK_INCOMPATIBLE_COLUMNS
RENAME TABLE parent0 TO parent;
--disable_testcase Bug#28608460
CREATE TABLE parent (pk INT PRIMARY KEY) ENGINE=MyISAM;
ALTER TABLE parent ENGINE=InnoDB;
--enable_testcase
DROP TABLES child, parent0;
SET FOREIGN_KEY_CHECKS=1;

--echo #
--echo # Tests for bug#28608460 "POSSIBLE TO ADD INCONSISTENT PARENT TO ORPHAN
--echo #                         FOREIGN KEY IF SE CHANGED".
--echo #

--echo #
--echo # Check that consistency checks are performed when we add parent
--echo # table to previously orphan foreign key by changing table storage
--echo # engine.
SET FOREIGN_KEY_CHECKS=0;
CREATE TABLE child (fk INT, FOREIGN KEY(fk) REFERENCES parent (pk)) ENGINE=InnoDB;
CREATE TABLE parent (pk INT) ENGINE=MyISAM;
--error ER_FK_NO_INDEX_PARENT
ALTER TABLE parent ENGINE=InnoDB;
DROP TABLE parent;
CREATE TABLE parent (a INT) ENGINE=MyISAM;
--error ER_FK_NO_COLUMN_PARENT
ALTER TABLE parent ENGINE=InnoDB;
DROP TABLE parent;
CREATE TABLE parent (pk BIGINT PRIMARY KEY) ENGINE=MyISAM;
--error ER_FK_INCOMPATIBLE_COLUMNS
ALTER TABLE parent ENGINE=InnoDB;
DROP TABLE parent;

--echo #
--echo # This should work for ALTER TABLE that combines change of SE
--echo # with renaming of table.
CREATE TABLE parent0 (pk INT) ENGINE=MyISAM;
--error ER_FK_NO_INDEX_PARENT
ALTER TABLE parent0 ENGINE=InnoDB, RENAME TO parent;
DROP TABLE parent0;

--echo #
--echo # ALTER TABLE which combines change of SE and renaming of the
--echo # table is executed as if we separately did change of SE and
--echo # renamed table after that. I.e. consistency checks are also
--echo # performed for orphan foreign keys which are associated with
--echo # old table name.
CREATE TABLE parent (pk INT) ENGINE=MyISAM;
--error ER_FK_NO_INDEX_PARENT
ALTER TABLE parent ENGINE=InnoDB, RENAME TO parent0;
DROP TABLE parent;

--echo #
--echo # Check that unique constraint name is correctly updated when parent
--echo # table is added to orphan foreign key by changing table SE.
CREATE TABLE parent (pk INT, UNIQUE u(pk)) ENGINE=MyISAM;
SELECT referenced_table_name, unique_constraint_name FROM
  information_schema.referential_constraints WHERE table_name = 'child';
ALTER TABLE parent ENGINE=InnoDB;
SELECT referenced_table_name, unique_constraint_name FROM
  information_schema.referential_constraints WHERE table_name = 'child';
DROP TABLE parent;

--echo #
--echo # Since ALTER TABLE which combines change of SE and renaming of the
--echo # table is executed as if we separately did change of SE and
--echo # renamed table after that, the referenced table name should
--echo # be updated too.
CREATE TABLE parent (pk INT PRIMARY KEY) ENGINE=MyISAM;
SELECT referenced_table_name, unique_constraint_name FROM
  information_schema.referential_constraints WHERE table_name = 'child';
ALTER TABLE parent ENGINE=InnoDB, RENAME TO parent0;
SELECT referenced_table_name, unique_constraint_name FROM
  information_schema.referential_constraints WHERE table_name = 'child';
RENAME TABLE parent0 TO parent;
DROP TABLES parent;

--echo #
--echo # Check that under LOCK TABLES, when adding parent for previously orphan
--echo # foreign key by SE change, we check locks on child tables.
CREATE TABLE parent (pk INT PRIMARY KEY) ENGINE=MyISAM;
LOCK TABLES parent WRITE;
--error ER_TABLE_NOT_LOCKED
ALTER TABLE parent ENGINE=InnoDB;
UNLOCK TABLES;
LOCK TABLES child READ, parent WRITE;
--error ER_TABLE_NOT_LOCKED_FOR_WRITE
ALTER TABLE parent ENGINE=InnoDB;
UNLOCK TABLES;
LOCK TABLES child WRITE, parent WRITE;
ALTER TABLE parent ENGINE=InnoDB;
UNLOCK TABLES;
DROP TABLES child, parent;
SET FOREIGN_KEY_CHECKS=1;