Bug #70122 Model looses typed data entry when switching tabs to query tool
Submitted: 22 Aug 2013 14:08 Modified: 5 Nov 2013 21:46
Reporter: mike coutinho Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.06 OS:MacOS
Assigned to: CPU Architecture:Any

[22 Aug 2013 14:08] mike coutinho
When typing into a trigger inside a model, I switched over to a tab to check something and when I switched back to the model, all the typed sql was gone!

How to repeat:
Open a model, type in something into a trigger, go to a query tab, go back and data is gone.
[22 Aug 2013 14:16] mike coutinho
as I continued playing, this seems to not affect statements that are correct (they don't have the red * in the front of the line saying that there is an error on that line).  If there is an error or the statement is complete, it nukes it when you come back to the trigger.
[22 Aug 2013 14:38] MySQL Verification Team
Please provide a statement which makes that issue happens. Thanks.
[22 Aug 2013 14:41] mike coutinho
If I am editing a trigger in my model(I have not tried anywhere else) and I have an incomplete sql statement in the trigger, when I switch over to a query tab to check on something, when I come back to the trigger in the model the incomplete sql statement I put in is gone.
[22 Aug 2013 17:07] MySQL Verification Team
Thank you for the feedback.
[27 Aug 2013 12:51] Mike Lischke
Bug #70108 was marked as duplicate of this one.
[30 Oct 2013 17:57] Armando Lopez Valencia
Posted by developer:
Verified in:
Windows 7x64
Ubuntu 12.04x64
OSX 10.8.4
MySQL Server 5.6
The trigger content is persistent even in OSX.
[5 Nov 2013 21:46] Philip Olson
Fixed as of MySQL Workbench 6.0.8, and here's the changelog entry:

After editing a trigger in the model tab, switching tabs (such as loading
a connection or SQL editor tab) would cause the new trigger edits to

Thank you for the bug report.