Bug #34168 | MySQL Workbench crashes when deleting columns | ||
---|---|---|---|
Submitted: | 30 Jan 2008 15:26 | Modified: | 29 Feb 2008 8:33 |
Reporter: | Daniel Haas | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.0.12 SE | OS: | Windows (Vista) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[30 Jan 2008 15:26]
Daniel Haas
[30 Jan 2008 15:27]
Daniel Haas
Screenshot showing the stacktrace.
Attachment: deleting_columns.png (image/png, text), 234.55 KiB.
[30 Jan 2008 15:27]
Daniel Haas
The complete text of the stacktrace.
Attachment: stacktrace.txt (text/plain), 7.86 KiB.
[30 Jan 2008 15:29]
Alfredo Kojima
Hi Would it be possible to attach a sample model? Thanks!
[30 Jan 2008 15:37]
Valeriy Kravchuk
What exact column should I try to delete after loading your model?
[30 Jan 2008 17: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 17:18]
MySQL Verification Team
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 8: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 8: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 0: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".