Bug #19315 | Duplicate Foreign Keys | ||
---|---|---|---|
Submitted: | 24 Apr 2006 21:37 | Modified: | 29 Jun 2006 17:45 |
Reporter: | TJ Bell | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench Preview | Severity: | S1 (Critical) |
Version: | 1.0.6 Beta | OS: | Windows (Windows XP SP2) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[24 Apr 2006 21:37]
TJ Bell
[24 Apr 2006 22:55]
MySQL Verification Team
Thank you for the bug report.
[25 Apr 2006 15:51]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=19337 marked as duplicate as duplicate of this one.
[2 May 2006 12:19]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=19467 was marked as duplicate of this one.
[5 May 2006 17:24]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=19556 was marked as duplicate of this one.
[30 May 2006 22:45]
Dominic Clifton
Seeing as it's been reported 4 times, might it not be a good idea that someone gets onto this right away as it's a rather major problem...
[31 May 2006 20:41]
Kael Fischer
Please increase the severity of this bug in the tracker. This is a total show stopper here.
[13 Jun 2006 8:13]
Wim Heemskerk
I'd like to second those last two comments. This is the top priority bug for me as well, the show stopper that made me set aside beta 1.0.6 as not yet useable.
[13 Jun 2006 16:28]
Stephen O
This definitely is a critical issue.
[23 Jun 2006 19:43]
Julien a
I wonder how it was decided that this bug is non critical, for me it is clearly a blocker. Each time I make any change to a table the foreign keys are duplicated, if you consider this as non critical then try to create a real schema with 10 or more foregn keys and you will see... The worse is that aside of this bug the application is useable.
[26 Jun 2006 2:00]
David Boccabella
Same Here. I imported a major sized database and needed to document it. Had a LOT of trouble with diplicate foreign key indicators Dave
[29 Jun 2006 15:15]
Gareth Gough
This is quite a frustrating bug, because this will be a great tool once out of the beta phase. I can see that this thread has been open for a while, and the ststus of the bug is at S1(critical), but for future reference, how did the severity get escallated? Gareth
[29 Jun 2006 17:45]
Alfredo Kojima
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html