Bug #66297 | Error Code: 1064 on "ADD CONSTRAINT" function | ||
---|---|---|---|
Submitted: | 10 Aug 2012 6:52 | Modified: | 16 Jul 2014 6:42 |
Reporter: | Steve Tse | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.41 | OS: | Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[10 Aug 2012 6:52]
Steve Tse
[10 Aug 2012 13:08]
Valeriy Kravchuk
I can not repeat this with 5.2.41 on Windows. Can you try to drop tables before running your script? Probably table already has same constraint, or other table definition is inherited.
[14 Aug 2012 9:05]
Steve Tse
I have tried to drop table and drop database, and then run the sql but no luck. Instead I tried to create a Foreign Key constraint via GUI, it works. So I copied the same script from the GUI and tried it again, there is no way to make it work in script.
[22 Aug 2012 2:31]
Steve Tse
Anyone have idea?
[31 Aug 2012 1:15]
MySQL Verification Team
Are you tried version 5.2.42 ?. Thanks.
[1 Oct 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[15 Apr 2014 9:10]
Vladimir Tisma
I have this in MySQL Workbench 5.2.47 on Ubuntu. Running from any other SQL client but Workbench is successful.
[16 Jun 2014 6:42]
MySQL Verification Team
I could not repeat this issue on latest GA version. Also, version 5.2.47 is old and many bugs were fixed since. Please upgrade to current version 6.1.6, try with it and inform us if problem still exists. http://dev.mysql.com/downloads/workbench/
[17 Jul 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".