Bug #44243 DEFAULT NULL not permitted for INT fields
Submitted: 13 Apr 2009 19:29 Modified: 20 Aug 2010 10:20
Reporter: Robert Cesaric Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.0.30, 5.2 OS:Windows
Assigned to: Maksym Yehorov CPU Architecture:Any
Tags: Default NULL, regression

[13 Apr 2009 19:29] Robert Cesaric 
Description:
When you create a column of type INT and you define DEFAULT NULL, the MySQL validation
tool (Model >> Validation (MySQL) >> Validate All) reports 'Invalid default value NULL'

This was reported in bug #38775 and closed but is still a problem (at least with version 5.0.30).

How to repeat:
1. design table t1 as:
    CREATE  TABLE IF NOT EXISTS `mydb`.`t1` (
      `id` INT NOT NULL AUTO_INCREMENT ,
      `x1` INT NULL DEFAULT NULL ,
      PRIMARY KEY (`id`) )
    ENGINE = InnoDB
2. select Model >> Validation (MySQL) >> Validate All

The log reports:
  Invalid default value 'NULL' for column `t1`.`x1`: .
[13 Apr 2009 21:11] MySQL Verification Team 
Thank you for the bug report.
[27 Oct 2009 7:46] Susanne Ebrecht 
This still happens in actual bzr tree of Workbench 5.2 (5.2.6)
[29 Jun 2010 20:51] Maksym Yehorov 
Fixed
[20 Aug 2010 10:20] Johannes Taxacher 
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/