MySQL Bugs: #50623: MySQL Workbench - Altering triggers using UI

Bug #50623	MySQL Workbench - Altering triggers using UI
Submitted:	26 Jan 2010 12:59	Modified:	27 Jan 2010 13:51
Reporter:	Arnaud Millereux	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.14 Beta	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	alter, MySQL Workbench, trigger

Description:
Hello MySQL Group,

We encounter some issues using MySQL Workbench 5.2.14 (Beta) when used in order to modify triggers previously created with success.

First, either the system shows an error when attempting to replace trigger (already exist !) by applying changes with the dedicated button or doesn't detect updates.

Next, there is no SQL commands in summary window whereas the system says everything is ok.

Next, there are some tab's refresh issues when using this tool.

In second case, there is no risk to lose programs, but in first one, we lose trigger content if we don't save it by a copy to clipboard before.

How to repeat:
Procedure :
1. Please, create a trigger by filling in the pane ;
2. Click on "Apply" (one or two times if it was a paste) ;
3. CLick on finish ;
4. Everything is Ok.

Now when you go back in trigger's pane, modify a little this one and click on Finish (1) or (2). See suggests below ...

Suggested fix:
1. If don't paste the trigger in summary window, no error but no update too.
2. If you paste it in summary and you want action really applied, the system says this trigger already exist. So you can make a "drop trigger xxx" by hand, validate and go back in order to paste true trigger. And now update is loaded.

This is a duplicate of bug #49287

Ok, I have just informed you because I didn't know if you had tried to correct this one since first beta release of MySQL Workbench.

Best regards