Bug #51490 Message Log of Reverse Engineer SQL Script wizard: Scrolbar not active
Submitted: 25 Feb 2010 8:47 Modified: 26 Feb 2010 21:33
Reporter: Kai Sautter (Basic Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.16 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: qc

[25 Feb 2010 8:47] Kai Sautter
Description:
The Message Log Box within the second step of the Reverse Engineer SQL Script wizard (called from the home tab using "Create EER Model from SQL Script") only displays 21 message lines. If there are more messages, any further message can not be read, though a scrollbar is present (but not active).

Unfortunately, the content of the text box can not be selected in its entirety using e.g. Ctrl-A, which would allow to copy the content to a text editor for review. This is also the reason for rating the bug as "S2" instead of "S3", which I would normally apply to a GUI bug.

How to repeat:
1) Create an SQL script holding e.g. 22 CREATE statements for tables and/or views or for a table with more than 20 columns with unsupported data types.
2) Reverse engineer this script to an EER model using the Reverse Engineer SQL Script wizard.
3) select "Show Logs" on the pane for the second step of the wizard

Suggested fix:
Activate scrollbar, if the number of message lines exceeds 21.
[25 Feb 2010 10:58] Kai Sautter
The reason for the scrollbar not being active might be, that the text field as such us larger than the canvas used to display it, or the fact that the text fields enabled property is set to false.
[26 Feb 2010 7:51] Susanne Ebrecht
Many thanks for writing a bug report.

Unfortunately, I can't follow you on the how to reproduce.

Please explain "click by click" what you did and where you think a scrollbar is needed.
[26 Feb 2010 8:56] Kai Sautter
Here is a more precise description of how to reproduce the described behavior:
1) Create an SQL script to create some tables, that will generate a sufficient amount of messages, e.g.
CREATE TABLE test1
	f1 BOOL,
	f2 BOOL,
	f3 BOOL,
	f4 BOOL,
	f5 BOOL;

CREATE TABLE test2
	f1 BOOL,
	f2 BOOL,
	f3 BOOL,
	f4 BOOL,
	f5 BOOL;

CREATE TABLE test3
	f1 BOOL,
	f2 BOOL,
	f3 BOOL,
	f4 BOOL,
	f5 BOOL;

CREATE TABLE test4
	f1 BOOL,
	f2 BOOL,
	f3 BOOL,
	f4 BOOL,
	f5 BOOL,
	f6 BOOL;

--- END OF SCRIPT ---

2) In WB go to the HOME tab
3) Select Create EER Model from SQL Script (Data Modeling section at the bottom)
4) Select the file with the above SQL script
5) Click "Execute"
6) Click "Show Logs" (bottom left of the Wizard pane)
7) Review Message Log
[26 Feb 2010 9:07] Kai Sautter
Having further analyzed this, the root cause of the problem could be, that the text box for the message log is too large (i.e. larger than the canvas used to display it), as there seems to be at least one invisible line in the log when using the example, I just provided.
[26 Feb 2010 9:35] Valeriy Kravchuk
Verified just as described in your last comments using the .sql file uploaded. Thank you.
[26 Feb 2010 21:33] Johannes Taxacher
this is a duplicate of bug #51417