Bug #39473 Database Synchronisation of datatype boolean failure
Submitted: 16 Sep 2008 10:35 Modified: 18 Nov 2008 16:35
Reporter: Lars Monecke Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.0.26 SE OS:Windows (XP 64)
Assigned to: CPU Architecture:Any

[16 Sep 2008 10:35] Lars Monecke 
Description:
Synchronisation of attached test.mwb failes to MySQL Server 5.0.x  because of "BOOLEAN(2)" send as datatype for "foobar":

CREATE  TABLE IF NOT EXISTS `mydb`.`table1` (
  `table1_id` INT(11) NOT NULL ,
  `foobar` BOOLEAN(2) NULL DEFAULT NULL ,
  PRIMARY KEY (`table1_id`) )
ENGINE = InnoDB
DEFAULT CHARACTER SET = latin1
COLLATE = latin1_swedish_ci;

How to repeat:
do a Database Synchronisation with attached mwb file

Suggested fix:
use boolean as datatype
[14 Oct 2008 15:30] Valeriy Kravchuk 
Thank you for a problem report. Please, try to repeat with a newer version, 5.0.26, and inform about the results.
[28 Oct 2008 6:27] Lars Monecke 
Same with 5.0.26 SE
[28 Oct 2008 6:27] Lars Monecke 
Workbench file

Attachment: test.mwb (application/octet-stream, text), 3.17 KiB.
[1 Nov 2008 19:28] MySQL Verification Team 
Thank you for the bug report.
[18 Nov 2008 16:35] Johannes Taxacher 
this is actually a dupe of this one:
http://bugs.mysql.com/bug.php?id=39257
which has been fixed in 5.0.27