Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
--source include/have_innodb.inc
|
|
CREATE TEMPORARY TABLE t (a INT, KEY(a)) ENGINE=InnoDB; |
INSERT INTO t VALUES (1); |
ALTER TABLE t DROP FOREIGN KEY fk; |
|
# Cleanup
|
DROP TABLE t; |
10.3 77951dd7 |
CREATE TEMPORARY TABLE t (a INT, KEY(a)) ENGINE=InnoDB; |
INSERT INTO t VALUES (1); |
ALTER TABLE t DROP FOREIGN KEY fk; |
DROP TABLE t; |
So, although there is no foreign key fk (or any other), ALTER succeeds.
Reproducible on all current version lines of MariaDB and on MySQL 5.7. Not reproducible on MySQL 8.0.
And yet, adding an invalid FK to a temporary InnoDB table causes typical "incorrectly formed" errors (unlike adding the same to a MyISAM table, which truly doesn't care). So if it's unsupported, it's inconsistently unsupported.