MySQL Bugs: #39257: exporting BOOLEAN gives BOOLEAN(2)

Bug #39257	exporting BOOLEAN gives BOOLEAN(2)
Submitted:	4 Sep 2008 20:27	Modified:	11 Nov 2008 10:54
Reporter:	Exception e	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.24	OS:	Windows
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
When a column has datatype BOOLEAN and one exports it (Forward Engineer SQL ALTER), the result is BOOLEAN(2) instead of BOOLEAN.

How to repeat:
DO:
define a column as BOOLEAN
export it, eg as Forward Engineer SQL ALTER

EXPECT:
column gets datatype BOOLEAN

ACTUAL RESULT:
column gets datatype BOOLEAN(2)

Thank you for the bug report.

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

ALTER TABLE `mydb`.`table1` ADD COLUMN `col3` BOOLEAN(2) NULL DEFAULT NULL  AFTER `col2` ;

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

Same thing happens too when using the Synchronize Function from the Database Menu.

It happens also in 5.0.26

This is fixed now. Fix will be included into 5.0.27.

for DB sync this is a different situation as MySQL stores BOOLEAN columns as TINYINT therefore we have to deal with this as a seperate problem.

An entry was added to the 5.0.27 changelog:

When a column had a datatype BOOLEAN and it was exported using Forward Engineer SQL ALTER, the exported type was BOOLEAN(2) instead of BOOLEAN.