[MDEV-22230] Unexpected ER_ERROR_ON_RENAME upon DROP non-existing FOREIGN KEY with ALGORITHM=COPY - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
Fix Version/s: 10.4.33, 10.5.24, 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3
Component/s: Data Definition - Alter Table, Storage Engine - InnoDB
Labels:
None

Description

--source include/have_innodb.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;

--error ER_CANT_DROP_FIELD_OR_KEY

ALTER TABLE t1 DROP FOREIGN KEY x, ALGORITHM=COPY;

# Cleanup

DROP TABLE t1;

10.5 8c0b9880

query 'ALTER TABLE t1 DROP FOREIGN KEY x, ALGORITHM=COPY' failed with wrong errno 1025: 'Error on rename of './test/t1' to './test/#sql2-10fa-4' (errno: 152 "Cannot delete a parent row")', instead of 1091...

Without ALGORITHM=COPY it fails with ER_CANT_DROP_FIELD_OR_KEY as expected.

There is an ancient upstream bug https://bugs.mysql.com/bug.php?id=14347 which seems related, but I'm not sure it's quite the same.

Attachments

Issue Links

relates to

MDEV-28904 DROP CONSTRAINT ..., ALGORITHM=COPY has no effect

Stalled

MDEV-20480 Obsolete internal parser for FK in InnoDB

Closed

MDEV-22232 Server crashes in rpl_sql_thread_info::cached_charset_compare / wsrep_apply_events

Closed

links to

Bug #14347 Can't remove FOREIGN KEY

Activity

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2020-04-13 16:14

Updated:: 2023-11-30 12:56

Resolved:: 2023-11-27 06:32

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.