Bug #55052 Right-click 'copy sql to clipboard' error alert
Submitted: 7 Jul 2010 11:55 Modified: 7 Aug 2010 12:37
Reporter: Christoffer Hafsahl Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.24 CE RC, rev 6246 OS:Windows
Assigned to: CPU Architecture:Any

[7 Jul 2010 11:55] Christoffer Hafsahl
Description:
I've built a database model with multiple tables. When right-clicking a table and selecting 'copy sql to clipboard' in the EER diagram, an error pops up alerting me that something went wrong. There is no specific error code. 

Subsequent repeats of the same action works fine with no errors. The copy itself also works on the first attempt despite the error.

Also, when closing MySQL Workbench, the GUI closes but the process remains in the process list (WinXP, SP3). This is a serious issue, as the process is left with around 100MB RAM, and continuously utilize one processor core at 100%. The only way to free these resources is to manually kill the process. This is only a problem if the error in question has been trigged.

How to repeat:
Start/restart MySQL Workbench. Select a table in the EER diagram, right click it, and select 'copy SQL to clipboard'.
[7 Jul 2010 12:03] Valeriy Kravchuk
Does it happen with any table or with specific one? Can you upload problematic .mwb file to this report?
[7 Jul 2010 12:27] Christoffer Hafsahl
After having rebooted my PC I can't reproduce the problem any longer. Before reboot however, it applied to any table in any .mwb file, both newly created and old ones. Also tested on tables with and without foreign keys, with identical results. 

I'll see if I can get some time to reproduce the problem properly later today.
[7 Jul 2010 12:37] Valeriy Kravchuk
If you'll repeat the problem, please, add the results from Help > System Info menu item also.
[7 Aug 2010 23: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".