MySQL Bugs: #49432: Routines SQL not updated if new Routine Group opened in editor

Bug #49432	Routines SQL not updated if new Routine Group opened in editor
Submitted:	3 Dec 2009 22:25	Modified:	20 Apr 2010 13:06
Reporter:	Kolbe Kegel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.10 Beta	OS:	Linux (mysql-workbench-oss-5.2.10-1ubu804-amd64.deb)
Assigned to:	Maksym Yehorov	CPU Architecture:	Any

Description:
If you have the Routine Group editor open and you open another Routine Group to edit it, the Routines SQL contents from the original Routine Group remains in the Routines tab.

The only way to view the SQL of another routine group is to close the Group editor entirely and edit the new Routine Group.

This can cause a great deal of confusion when trying to view the contents of a Routine Group and could lead to lost/overwritten data.

How to repeat:
1) Open sakila.mwb (or some other Model with multiple Routine Groups defined)
2) Double-click a Routine Group to open it in the editor
3) Switch to the Routines tab of the Group editor
4) Double click a different Routine Group to open it in the editor
5) Note that the contents of the Routines tab still shows the SQL from the previous Routine Group

Suggested fix:
The contents of the Routines tab should be updated when a new Routine Group is opened in the editor.

Fixed.

fix confirmed in repository

An entry has been added to the 5.2.19 changelog:

When two routine groups were being edited, and in both cases the Routines tab was selected to display the SQL code, switching between the routine groups did not result in the target Routines tab contents being updated. For example, if routines1 was being displayed and the routines2 selected, the routines1 code continued to be displayed in the Routines tab.