MySQL Bugs: #33367: table with lots of columns don't display correctly

Bug #33367	table with lots of columns don't display correctly
Submitted:	19 Dec 2007 14:31	Modified:	26 Feb 2008 14:27
Reporter:	pierre mottin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.12 OSS Beta	OS:	Windows (XP SP2 Fr)
Assigned to:	Johannes Taxacher	CPU Architecture:	Any

Description:
A table with 190 columns don't display correctly.

When the table is expanded, it's impossible to scroll down and view the all table (table is out of the aera),  
impossible to move the expanded table,
impossible to zoom + or - without very buggy canva redrawing,
the application slow down a lot when expanding the collapsed big table,
the app sometimes crashes (application stops responding, must kill the app),
and very often the big table is invisible in the ERR Diagram aera after a zoom change.

How to repeat:
Just create a big table with lot of colums and try using it :
- expand/collapse
- move table in the ERR
- change the zoom level

A precision :

impossible to move "correctly" the expanded table : when starting to drag the table somewhere else in the aera the table "dock" at the top. Then the title bar is not accessible (out of the aera) ; must use Arrange/Autolayout to gain access to the table

Upgrade to 5.0.12 : OSS stops responding when i'm trying to work with the big table (expand/collapse) in my huge database. Impossible to work.

create script of a really-many-columns-table

Attachment: huge_table_create.sql (application/octet-stream, text), 3.39 KiB.

You can use the uploaded create-script to reproduce the problem. the "docking"-behaviour seems to originate from the functionality to try to keep objects fully inside its parent-boundaries.

If you import the script and drop it on a new EER-View it immediately dissapears. I was able to reveal it by lowering the zoom-level

The improved sw rendering solves the drawing problems.
If the table titlebar disappears its because the model is too small to fit the table,
you should increase the diagram size in Model -> Diagram Size...
However, the algorithm to try keeping objects inside the model was changed
so that the title won't be moved outside it.

long tables now keep their top inside the pages ... for viewing them completely you have to enlarge the diagram size.
We're thinking about the possibility to let user shrink table-heights down so that not all columns are displayed.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
Added to the changelog and noted in the body of the documentation.