Bug #55456 default value 'null' + not null results in script that executes with error
Submitted: 21 Jul 2010 19:20 Modified: 4 Jan 2011 17:43
Reporter: Andrei Frolov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.25 CE OS:Windows
Assigned to: Mike Lischke CPU Architecture:Any
Tags: default value, NOT NULL

[21 Jul 2010 19:20] Andrei Frolov 
Description:
In table properties WB allows to set default value NULL if Not NULL is set for column. This results in Error 1067 during script execution.

How to repeat:
Add new table to EER diagram. Add column, check NN, set default value to NULL.
Execute 'Forward engineer' or 'Synchronize model' command. 

Suggested fix:
remove default value 'NULL' if 'not null' is chosen.
[21 Jul 2010 22:33] MySQL Verification Team 
Thank you for the bug report.
[23 Jul 2010 16:45] Johannes Taxacher 
Workbench SE version does have a validation module that alerts user about such a problem, in community edition user has to take care of such "misconfigurations" himself. We will improve that in future versions.
[15 Nov 2010 15:53] Mike Lischke 
Fixed in repository.
[8 Dec 2010 23:11] Johannes Taxacher 
fix confirmed in repository
[4 Jan 2011 17:43] Tony Bedford 
An entry has been added to the 5.2.31 changelog:

In the Column tab of the Table Editor, it was possible to set NULL as the default value for a column that had been specified as NOT NULL.