MySQL Bugs: #33519: Table editor allow emtpy string in Datatype Field

Bug #33519	Table editor allow emtpy string in Datatype Field
Submitted:	26 Dec 2007 23:16	Modified:	17 Jan 2008 15:06
Reporter:	Edwin Cruz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.11	OS:	Windows (XP Profesional sp2)
Assigned to:	Johannes Taxacher	CPU Architecture:	Any
Tags:	datatype, export, import, reverse engineering

Description:
Table editor allow emtpy string in Datatype Field.
This issue could cause that when the model is Exported then Imported(in mysql or workbench using reverse engineering) or sinchronized a sql sintaxis error will be throw.

How to repeat:
Create a new table in the EER Diagram
Edit the table and add some columns
Select the datatype for any row and delete its value
Close the table editor

An issue that I've experimented is:
Create a table with a column without datatype
Export as Forward Engneer SQL CREATE SCRIPT
The same file Import using Reverse Engineer MySQL Create Script
Press Ctr+F2 to see the output and nothing is imported but a message like this is printed:
Started parsing MySQL SQL script.
Previously created MySQL Schema `mydb`was found. Statement ignored
<blank line>
Finished parsing MySQL SQL script. Totally processed statements: successfull (1), errors(1), warnings(1).

in <blank line> should have the output with this kinda label:
Created MySQL table: mydb.TableName 

Suggested fix:
Create a default datatype or
Create a warning/error message about the issue

Thank you for the bug report.

I will add a check into validation-module.
we'll integrate an auto-validate switch later on.

a new verification module is now in place which warns about columns that don't have types specified