Bug #30747 | Create table with identical constraint names behaves incorrectly | ||
---|---|---|---|
Submitted: | 31 Aug 2007 10:23 | Modified: | 24 Oct 2007 20:09 |
Reporter: | Jan Lindström | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 & 5.1 | OS: | Any |
Assigned to: | Davi Arnaut | CPU Architecture: | Any |
[31 Aug 2007 10:23]
Jan Lindström
[6 Sep 2007 17:00]
Konstantin Osipov
Davi, please check and apply the suggested patch. Do not implement the uniqueness check, since this is a distinct bug/feature request (we plan to do it separately in 6.1 or later). Fix in 5.1 please.
[13 Sep 2007 22:22]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/34224 ChangeSet@1.2611, 2007-09-13 19:22:08-03:00, davi@moksha.local +3 -0 Bug#30747 Create table with identical constraint names behaves incorrectly MySQL provides what appears to be a non standard extension to the FOREIGN KEY syntax which let users name (label/tag) a foreign key to more easily identify a specific foreign key if any problems show up later during the query parsing or execution. But the foreign key name was not being properly set to the right key, possible leaving the foreign key with no name.
[27 Sep 2007 15:06]
Davi Arnaut
Pushed into mysql-5.1-runtime
[19 Oct 2007 18:53]
Bugs System
Pushed into 5.1.23-beta
[24 Oct 2007 19:47]
Paul DuBois
Noted in 5.1.23 changelog.