Bug #44098 Invalid Triggers Not Saved

• Submitted: 5 Apr 2009 19:31
• Modified: 8 Jul 2009 10:58
• Reporter: Jason Hendrix
• Status: No Feedback
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.0.30
• OS: Windows
• CPU Architecture: Any
• Tags: CHECKED, save, triggers

[5 Apr 2009 19:31] Jason Hendrix

Description:
If a trigger statement is invalid, no message is presented to indicate there is an error and the statement is not saved.

How to repeat:
1. From the MySQL Model tab double click a table (table A).
2. Click the Triggers tab.
3. Type a bogus trigger statement (specifically one that references a table that does not exist).
4. Double click another table (table B) in the tables listing on the MySQL Model tab.
5. Double click table A again and the the trigger will be missing.

[5 Apr 2009 19:56] Valeriy Kravchuk

Thank you for the bug report. Verified just as described.

[8 Jun 2009 10:58] Mike Lischke

This problem is not reproducible in MySQL Workbench 5.1. So, please check with that version. We are focusing on WB 5.1 and would like to fix this problem there if it still exists, rather than WB 5.0. Thank you.

[8 Jul 2009 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".