Bug #36360 using flags in default column type definition fail to display correctly.
Submitted: 27 Apr 2008 4:25 Modified: 6 Feb 2013 15:36
Reporter: walter stanish Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.0.19 OS:Any (XPSP2)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: column, flags, interface, type, UNSIGNED

[27 Apr 2008 4:25] walter stanish 
Description:
setting INT UNSIGNED as the default primary key column type in the model options generates tables that fail to display correctly: unsigned flag is not set, column type is empty not INT.

How to repeat:
set INT UNSIGNED as the model options > primary key column type.
create a table.
table display is broken... unsigned flag is not set, column type is empty not INT.

Suggested fix:
when creating a table, parse the column type in to primary type and flags, set appropriate flags.
[28 Apr 2008 12:03] MySQL Verification Team 
Thank you for the bug report.
[20 Oct 2009 11:17] Susanne Ebrecht 
Bug #40194 is set as duplicate of this bug here.
[6 Feb 2013 15:36] Alfredo Kojima 
Duplicate of bug #38802