MySQL Bugs: #39151: Columns name or dataType must be mandatory

Bug #39151	Columns name or dataType must be mandatory
Submitted:	1 Sep 2008 7:53	Modified:	1 Sep 2008 12:07
Reporter:	Lorenzo Luconi Trombacchi	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.24	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
At present you can create a column without a dataType or create a column and rename it to an empty name!

Export create sql script results for an unnamed column:

CREATE  TABLE IF NOT EXISTS `mydb`.`table1` (
  `idtable1` INT NOT NULL ,
  `` VARCHAR(45) NULL ,
  PRIMARY KEY (`idtable1`)
) ENGINE = InnoDB;

Export create sql script results for a column without datatype:
CREATE  TABLE IF NOT EXISTS `mydb`.`table1` (
  `idtable1` INT NOT NULL ,
  `a`  NULL ,
  PRIMARY KEY (`idtable1`) )
ENGINE = InnoDB;

How to repeat:
See description

this is expected behaviour. users may want to design models without specifying datatypes (first, or at all).
SE version features a validation plugin that warns users on export/sync about left blank datatypes (in OSS user has to take care of that himeslf)

Thank you for you answer.

Ok for datatype, I take care of missing datatypes myself. If is it an expected behaviour, how can unset a datatype for a column?

What about renamed to blank column name?
The validation is a feature of SE version, but at least the name of the column should be mandatory I think :-))

Lorenzo