MySQL Bugs: #51172: Unknown Exception caught ... Wb.h at line 1122

Bug #51172	Unknown Exception caught ... Wb.h at line 1122
Submitted:	14 Feb 2010 18:37	Modified:	16 Mar 2010 18:45
Reporter:	Halbert Stone	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.15b	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Unknown Exception caught in C:\documents and settings\mysqldev\build\mysql-workbench-oss-5.2.11\backend\windows\wbprivate.wr\src\Wb.h at line 1122

I was performing a sync from Model to data base when an alert displayed with the Unknown Exception msg. (NOTE: the path does not exist on my system)

I found different Errors reported when I showed the logs.  I suspect the Unknown Exception corresponds to there being an error during the sync.

Error msg I found that triggered the alert dialog are:

ERROR: Error 1105: Too long comment for table 'LogEventType'

ERROR: Error 1227: Access denied; you need the SUPER privilege for this operation

ERROR: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ,
  INDEX `fk_LoginEvent_Person1` (`Person_ID` ASC) ,
  INDEX `fk_LoginEvent_L' at line 7

How to repeat:
It seems to occur each time I try to sync Model to DB and there is an error as noted in the description (Errors #1105, #1227, and #1064)

Hi Halbert,

could you please check if you see this behavior still in latest available release (5.2.15)?
thanks in advance

Problem still exists in v5.2.15b Rev5053
Alert Dialog text:
"Unknown Exception caught in c:\documents and settings\mysqldev\build\mysql-workbench-oss-5.2.15b\backend\windows\wbprivate.wr\src\Wb.h at line 1087"

---------- Log content:
Executing SQL script in server

ERROR: Error 1227: Access denied; you need the SUPER privilege for this operation

CREATE TRIGGER InvalidCredentials
AFTER UPDATE ON Person
FOR EACH ROW
BEGIN
    IF attempts>2 then

      INSERT INTO `LoginEvent` (`idLoginEvent`, `Instance`, `Person_ID`, `LogEventType_idLogEventType`) 

      VALUES (0 ,NOW() ,OLD.Person_ID ,(select `idLogEventType` from `LogEventType` where `type` like '%Failure%'));

    END IF;
END
SQL script execution finished: statements: 5 succeeded, 1 failed

What version of MySQL server are you working with? Had you tried to connect as root or any other user with SUPER privilege?

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".