Bug #34168 MySQL Workbench crashes when deleting columns
Submitted: 30 Jan 2008 16:26 Modified: 29 Feb 2008 9:33
Reporter: Daniel Haas
Status: No Feedback
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.12 SE OS:Microsoft Windows (Vista)
Assigned to: Sveta Smirnova Target Version:

[30 Jan 2008 16:26] Daniel Haas
Description:
It just occured me that workbench crashed when deleting (multiple) columns. (See attached
screenshot).

After clicking on "Weiter" (continue) on the message box, all columns still stay there,
but the last one (the one which was under the mouse when right clicking) is suddenly no
index-column anymore. (The key-icon is replaced with the standard diamond-icon). -
Perhaps that helps in diagnosing the error.

I will attach the stacktrace and the workbench-file which shows the error.

How to repeat:
Appearently this only happens if the selected columns are columns automatically created
from a foreign-key constraint. - That means columns which refer to indexed data in the
foreign-table.

Note: This columns come from a DBDesigner4-imported file which automatically creates such
columns.

- I just found out that this happens also when just deleting one of these columns. MySQL
Workbench always crashes when deleting one of these columns.

So to repeat:
1. Create a model with foreign-key constraints in DBDesigner4
2. Import the model within workbench
3. Try to delete one of the autogenerated columns from the foreign table.

Suggested fix:
MySQL Workbench should just delete the columns as expected.
[30 Jan 2008 16:27] Daniel Haas
Screenshot showing the stacktrace.

Attachment: deleting_columns.png (image/png, text), 234.55 KiB.

[30 Jan 2008 16:27] Daniel Haas
The complete text of the stacktrace.

Attachment: stacktrace.txt (text/plain), 7.86 KiB.

[30 Jan 2008 16:29] Alfredo Kojima
Hi

Would it be possible to attach a sample model? Thanks!
[30 Jan 2008 16:37] Valeriy Kravchuk
What exact column should I try to delete after loading your model?
[30 Jan 2008 18:08] Daniel Haas
As visible in the screenshot, try to delete one of the trains_* columns in the
train_run_messages table.
These are the auto generated columns which originally just refer to the keys in the
foreign table trains.
[30 Jan 2008 18:18] Miguel Solorzano
I wasn't able to repeat using the model provided and instructions with
your last comment:'As visible in the screenshot, try to delete one of the trains_*
columns in the train_run_messages table.'. I tried on XP and I am asking to co-worker to
try on Vista.
[31 Jan 2008 9:05] Daniel Haas
Unfortunatly, after restarting Workbench and loading the file I had attached, i wasn't
able to reproduce the bug. - Sorry. Yesterday it happend for me on every row, and i was
only able to delete them once they went from key-icon to diamond-icon (by pressing
continue in the error dialog).
I keep you posted if i encounter the bug again.
[31 Jan 2008 9:33] Sveta Smirnova
Daniel, thank you for the additional information.

Set sttus of bug to "Need feedback" as your feedback is needed.
[1 Mar 2008 1:01] 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".