Bug #32363 Reporting: unique index not marked as unique
Submitted: 14 Nov 2007 9:49 Modified: 11 Aug 2009 14:29
Reporter: Ulf Wendel Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.8 SE (RC) OS:Windows
Assigned to: CPU Architecture:Any
Tags: CHECKED

[14 Nov 2007 9:49] Ulf Wendel
Description:
Reports seen to get the UNIQUE column wrong for unique indices.

Please note this is about WB 5.0.8. Beta SE. 5.0.8 Beta SE is newer than 1.1.10. You can download it from https://inside.mysql.com/wiki/MySQLWorkbenchAlphaReleases#Beta_Release_5.0.8 . Please note also the special and temporary handling of these "pre public beta" bug reports.

How to repeat:
Create a table like this:

CREATE  TABLE IF NOT EXISTS `mydb`.`table1` (`idtable1` INT NOT NULL , `col1` VARCHAR(45) NULL , PRIMARY KEY (`idtable1`) , UNIQUE INDEX idx1 (`col1` ASC) ) ;

It is *IMPORTANT* that you create the table in WB but do not reverse engineer/import it. Only if you create it inside WB, WB gets it wrong.

Export a single-page HTML report. Note the unique column, it says "NO".
[11 Aug 2009 14:29] Alfredo Kojima
This was already fixed previously.