Bug #64454 Routine Groups Can Not Be Resized
Submitted: 25 Feb 2012 20:49 Modified: 27 Feb 2012 5:00
Reporter: Matthew Kastor Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version:5.2.37, 5.2.38 OS:Any
Assigned to: CPU Architecture:Any
Tags: EER, model, resize, routine groups

[25 Feb 2012 20:49] Matthew Kastor
Routine groups can not be resized in EER Diagrams. It seems that the width of the routine group is determined by the length of the routine group's name and the selected font. The height of the routine group appears to be controlled by the length of the list of routines added to the group.

The reason I'd like to resize the routine group is because some of my routines have longer names than the routine group. This causes the routine names to be truncated and makes it pointless to even display the names of many of the included procedures. If I could increase the width of the routine group so that the full name of all included routines would be displayed then using the routine groups in the EER model would be much more effective.

As it is right now, using routine groups is the only way for me to display stored procedures. . . I think. If there is another way of showing the stored procedures in the EER model I might do that instead, it's just that I like grouping them together. The groups let me sort code, display a coherent summary (almost), and (nearly) give a good overview of the database.

MySql Workbench is an awesome tool, I think adding this simple feature would make it even better. XD

How to repeat:
Create a routine group with a short name. Add stored procedures to the routine group that have longer names. Add the routine group to the EER model. Note the truncation of names inside the displayed routine group. Note the ineffectiveness of trying to resize the routine group. Comment on this bug report / feature request.

Suggested fix:
Do whatever coding is required to make the resize boxes functional so we can drag them around and such.
[27 Feb 2012 5:00] Valeriy Kravchuk
Thank you for the problem report.