Bug #66310 | error creating a FK on the modeling tool | ||
---|---|---|---|
Submitted: | 10 Aug 2012 16:25 | Modified: | 16 Oct 2012 2:26 |
Reporter: | Ederson Sparenberger | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 5.2.41 | OS: | Windows (Microsoft Windows XP Professional Service Pack 3 (build 2600)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[10 Aug 2012 16:25]
Ederson Sparenberger
[10 Aug 2012 17:15]
Valeriy Kravchuk
Can you upload .mwb file that demonstrates the problem?
[10 Aug 2012 17:22]
Ederson Sparenberger
.mwb file that demonstrates the problem
Attachment: ER_crmGO.mwb (application/octet-stream, text), 35.80 KiB.
[10 Aug 2012 17:40]
Ederson Sparenberger
I belive the error was caused because i was trying to create a FK with the field PROD_PRODUTO.CODIGOSITUACAOPRODUTO(varchar(1)) , referencing PROD_SITUACAOPRODUTO.CODIGOSITUACAOPRODUTO (int). And the field PROD_PRODUTO.CODIGOSITUACAOPRODUTO was incorrectly set as varchar.
[10 Aug 2012 18:27]
Valeriy Kravchuk
And what exact FK should I try to create with your .mwb to reproduce the problem?
[10 Aug 2012 18:43]
Ederson Sparenberger
- Scroll down to the botton of the model, to the table prod_produto. - double click or right click it, "Edit table". It wont let you. - try to edit any other table, see if it allows you. - If it allowed you, try to edit prod_produto again - if it didnt alow you to edit prod_produto, cut and paste prod_produto on the model - now it allows you to edit it. - go to the foreign key tab, and create a FK_PRODUTOSITUACAOPRODUTO, referencing PROD_SITUCAOCAOPRODUTO with the fields CODIGOSITUACAOPRODUTO. The error should show itself on some point of those steps.
[16 Sep 2012 2:26]
MySQL Verification Team
I can't repeat with 5.2.43 . Please try it. Thanks.
[17 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".