Bug #36548 | If primary key column renamed, foreign key references must use original name | ||
---|---|---|---|
Submitted: | 6 May 2008 21:40 | Modified: | 7 May 2008 9:15 |
Reporter: | Anonymous Anonymous | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1.23-rc | OS: | MacOS (Leopard) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | foreign key, rename |
[6 May 2008 21:40]
Anonymous Anonymous
[6 May 2008 22:12]
Anonymous Anonymous
I just downloaded and installed the latest version at the time of this writing (5.1.24-rc) and confirmed that this bug still exists in the latest version.
[6 May 2008 22:20]
MySQL Verification Team
Looks like duplicate of bug: http://bugs.mysql.com/bug.php?id=21704.
[6 May 2008 22:42]
Anonymous Anonymous
But according to http://bugs.mysql.com/bug.php?id=21704 : ---- snip ---- [15 Feb 12:25] Alexander Nozdrin Just added a test case. The bugs is not repeated in 5.1.24-rc ---- end snip ---- Yet, I confirmed that the problem I've identified above still exists in 5.1.24-rc. Are you certain it's the same issue?
[6 May 2008 22:55]
MySQL Verification Team
I will test against the latest source, so if your case is repeatable so still there is an issue here.
[7 May 2008 9:15]
Heikki Tuuri
This problem of foreign keys under a column rename is a known problem. MySQL's upcoming SQL layer foreign keys may fix the problem in the coming years.