Bug #72069 Trigger name is being reset to default while editing
Submitted: 18 Mar 2014 16:02 Modified: 10 Sep 2014 11:08
Reporter: Sergii Golubev Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.0.8.11354 OS:Linux (Ubuntu)
Assigned to: CPU Architecture:Any
Tags: trigger

[18 Mar 2014 16:02] Sergii Golubev
Description:
Input "Trigger Name" on the "Triggers" tab has a bug - it resets to the default value. See "How to repeat".

How to repeat:
Try to add a trigger:

- 1. click "Alter Table..." on some table in Schemas tab and open "Triggers" tab in the table editing tab you opened

- 2. select some trigger in the left list of table's triggers and press button "Add trigger"

- 3. change trigger name, e.g. from "table_name_AUPD" to "table_name_after_update"

- 4. edit trigger body, e.g. add "BEGIN" and "END$$" on the next line

- 5. then:
- 5.1. switch to other application running in your OS by Alt+Tab, then switch back to the WorkBench - you'll see that the trigger's name had changed to it's default value
OR
- 5.2. simply focus "Trigger Name" input - it will change to the default value
[18 Mar 2014 17:21] MySQL Verification Team
Please try version 6.1.2. Thanks.
[19 Mar 2014 8:22] Sergii Golubev
I tried 6.1.2.11661 for Ubuntu 12.04. Very strange - in this new version the input "Trigger Name" is not editable for me. It looks like active but I am not able to change its content.
[10 Sep 2014 4:15] Alfredo Kojima
We removed the ability to edit the trigger name in a separate box, since it's usefulness is questionable and as you see, could cause problems. You can edit the trigger name directly in the trigger code instead.
[10 Sep 2014 11:04] Sergii Golubev
Nice idea to make the trigger's name input disabled.

But as for me, the input now looks quite strange - you can give it a focus, even move the text editing cursor in it, but can not edit. So the input does not look like disabled (e.g. grayed out, not focusable) and a user can not edit it. I think that this is not a predictable interface behavior and it may confuse users.
[10 Sep 2014 11:08] Sergii Golubev
Perhaps, it is better to completely remove 'Trigger Name' and 'Definer' inputs. Users that do use triggers are competent enough to find this information in the trigger's definition code.

I think that this can make the interface more straightforward.