Bug #77400 Forward enginer includes COMMENT ''

• Submitted: 18 Jun 2015 8:44
• Modified: 21 Sep 2015 22:52
• Reporter: Henrik Gemal
• Status: Closed
• Category: MySQL Workbench: Migration
• Severity: S5 (Performance)
• Version: 6.3.4
• OS: Windows (Microsoft Windows 7 Professional Service Pack 1)
• CPU Architecture: Any
• Tags: WBBugReporter

[18 Jun 2015 8:44] Henrik Gemal

Description:

when ever I forward engineer the database in version 6.3.4
I get column names like:

  `email` VARCHAR(90) NOT NULL COMMENT '', 

in version 6.3.3. I got:
  `email` VARCHAR(90) NOT NULL, 

please remove those empty comments

How to repeat:
forward engineer

[18 Jun 2015 9:27] MySQL Verification Team

Hello Henrik Gemal,

Thank you for the report.

Thanks,
Umesh

[18 Jun 2015 9:28] MySQL Verification Team

## On Win7
WB 6.3.4 (In the Review the SQL code to be executed window)
-- -----------------------------------------------------
-- Table `mydb`.`Bug77400`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`Bug77400` (
  `idBug77400` INT NOT NULL COMMENT '',
  `Bug77400col` VARCHAR(45) NOT NULL COMMENT '',
  PRIMARY KEY (`idBug77400`)  COMMENT '')
ENGINE = InnoDB;

WB 6.3.3 (In the Review the SQL code to be executed window)

-- -----------------------------------------------------
-- Table `mydb`.`Bug77400`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`Bug77400` (
  `idBug77400` INT NOT NULL,
  `Bug77400col` VARCHAR(45) NOT NULL,
  PRIMARY KEY (`idBug77400`))
ENGINE = InnoDB;

But, in both the cases on server it is stored as:

ushastry@myhostname [mydb]> show create table Bug77400\G
*************************** 1. row ***************************
       Table: Bug77400
Create Table: CREATE TABLE `Bug77400` (
  `idBug77400` int(11) NOT NULL,
  `Bug77400col` varchar(45) NOT NULL,
  PRIMARY KEY (`idBug77400`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

[17 Sep 2015 21:19] Omar Mendez Andrade

FIXED
MySQL Server 5.6.20, 5.7.8
MySQL Workbench 6.3.5
Ubuntu 15.04
OL7
Windows 8

Using file: mydb.mwb

-- -----------------------------------------------------
-- Schema mydb
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ;
USE `mydb` ;

-- -----------------------------------------------------
-- Table `mydb`.`Bug77400`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`Bug77400` (
  `idBug77400` INT NOT NULL,
  `Bug77400col` VARCHAR(45) NOT NULL,
  PRIMARY KEY (`idBug77400`))
ENGINE = InnoDB;

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

[21 Sep 2015 22:52] Philip Olson

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the changelog entry:

Forward Engineering would sometimes append "COMMENT ''" to column
definitions.

Thank you for the bug report.