MySQL Bugs: #23078: UNSIGNED incorrectly included for CHAR fields

Bug #23078	UNSIGNED incorrectly included for CHAR fields
Submitted:	7 Oct 2006 21:31	Modified:	10 Oct 2006 0:21
Reporter:	Matthew Williams	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S3 (Non-critical)
Version:	1.1.3 alpha	OS:	Windows (XP Home SP2)
Assigned to:		CPU Architecture:	Any

Description:
When you switch a field from INT to CHAR Workbench does not erase the "UNSIGNED" flag even though it does not apply to a CHAR. The same is true for "ZEROFILL" as well.

How to repeat:
Create a table.
Edit the table and add the first column. Workbench will automatically suggest the column name "idtable_01" which is fine.
Tab to the Datatype field and Workbench will automatically suggest "INT" and set the "UNSIGNED" flag. Change the Datatype field to "CHAR(5)" and tab to the next field. The "UNSIGNED" flag no longer is visable but it is still set.
Apply your table changes.
Export an SQL create script and you will see that it includes the "UNSIGNED" flag.

Suggested fix:
Clear flags when changing data types.

Thank you for the bug report. Verified with version 1.1.3.