MySQL Bugs: #43094: ignoring boolean datatype

Bug #43094	ignoring boolean datatype
Submitted:	22 Feb 2009 22:38	Modified:	6 Apr 2009 15:48
Reporter:	Hans Ginzel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.7	OS:	Linux (.deb, Ubuntu 8.10)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	boolean datatype, CHECKED

Description:
When reverse engineer sql script boolean data types were ignored. The type of a column in table editor was empty.

How to repeat:
Edit file test_boolean.sql with content
CREATE TABLE t1 (b boolean);
In Workbench try reverse engineer sql script.
See the table columns.

Workbench 5.1.7 just crashes for me on Ubuntu 8.04 during reverse engineering, so we definitely have a problem here.

I use Ubuntu 8.10, but 8.04 should probable be also supported because it is with Long Term Support.

This needs deeper analysis ... crash is not the behaviour of original reported bug. Maybe we have to deal here with two different bugs.

Started parsing MySQL SQL script.
Created MySQL Table: mydb.a
WARNING: Mapping failed for datatype `boolean`
Created MySQL Table: mydb.t
Finished parsing MySQL SQL script. Totally processed statements: successful (2), errors (0), warnings (1).
Operation failed: Module WbModel doesn't have function autoplace_ex

simple sql script with two tables ... one with an integer column, second with a boolean column

Attachment: booltest.sql (text/x-sql), 78 bytes.

This issue has been fixed in version 5.1.9 beta.

fix confirmed in 5.1.9

An entry was added to the 5.1.9 changelog:

When a script was processed by File, Import, Reverse Engineer MySQL CREATE Script, columns with a boolean data type had their data type ignored. As a result, the type of the column in the Table Editor was empty.

This bug, as described on 11 Mar 2009 14:01 Susanne Ebrecht is still present in version 5.2.29 CE Revision 6756 (downloaded today, Windows 7). Reverse engineering her booltest.sql still gives an empty datatype for t.b