Bug #35601 Unknown Exception caught when changing to "Connect to Columns"-notation
Submitted: 27 Mar 2008 12:05 Modified: 8 Apr 2008 14:20
Reporter: Daniel Haas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.16 RC OS:Windows (Vista)
Assigned to: Alfredo Kojima CPU Architecture:Any

[27 Mar 2008 12:05] Daniel Haas
Description:
I was just testing the different notations, when changing to the connect to columns notation crashed MySQl Workbench. (See Screenshot)
The error message showed this text:

Unknown Exception caught in c:\documents and settings\mysqldev\my documents\visual studio 2005\projects\mysql-workbench-pro\backend\windows\wb.wr\src\Wb.h at line 982

After clicking Ok, Workbench continued to work, but did not display the connect to columns-notation, alltough it was shown as selected in the menu.

Changing to another notation and then trying again with the connect to columns-notation, surprisingly worked.

How to repeat:
I tried to repeat it but did not manage to do it, sorry.
[27 Mar 2008 12:07] Daniel Haas
Unfortunatly I just saw that the screenshot i made was only black, so sorry no screenshot here. Basically it showed the message box and the text mentioned above. Interestingly it was not the standard exception dialog, but a normal message box with text in it. - If that helps in any way. :-)
[27 Mar 2008 12:10] Daniel Haas
Screenshot with the message

Attachment: connecting-columns-notation.png (image/png, text), 121.50 KiB.

[27 Mar 2008 12:11] Daniel Haas
As you see, I had the screenshot still in memory and was able to save it again. :-)
[27 Mar 2008 16:14] Johannes Taxacher
reproducable exactly as described with the model from http://bugs.mysql.com/bug.php?id=35598.
[28 Mar 2008 4:22] Alfredo Kojima
I could not repeat this after fixing the other related bugs. So it was probably caused by the same thing.
[28 Mar 2008 18:07] Johannes Taxacher
yes, not repeatable after alfredos fixes. tested with SVN Rev 2888
[8 Apr 2008 14:20] MC Brown
A note has been added to the 5.0.17 changelog: 

Switching to the Connect to Columns notation with an existing model would cause an exception.