MySQL Bugs: #34504: Forward Engineer and TRADITIONAL SQL Mode

Bug #34504	Forward Engineer and TRADITIONAL SQL Mode
Submitted:	12 Feb 2008 22:24	Modified:	29 Mar 2012 3:23
Reporter:	Sergey Romanov	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.13 SE Beta	OS:	Windows (XP SP2)
Assigned to:		CPU Architecture:	Any
Tags:	forward engineer, sql mode

Description:
After export with File > Export > Forward Engineer SQL CREATE Script I can see 
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';
in SQL file. But this mode create problems in some case. For example when you have '0000-00-00' as default value for date fields. In documentation you can see that TRADITIONAL is equivalent to STRICT_TRANS_TABLES, STRICT_ALL_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER. As result you have error when try to execute SQL from file.

How to repeat:
SQL:

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';

CREATE  TABLE IF NOT EXISTS `test` (
  `create_date` DATE NOT NULL DEFAULT '0000-00-00'
);

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

Result:

#1067 - Invalid default value for 'create_date' 

Suggested fix:
Export should be more smart.

Thank you for a bug report.

The TRADITIONAL mode is used my intention, so it's not a bug. But we recognize that it would be a good feature to allow users optionally choose a less strict operation mode (at their own risk). So I'm changing this to feature request.

the defualt SQL_MODE='TRADITIONAL' is a problem for me too, for which version is it's planned to allow users optionally choose a less strict operation mode?

Marked Bug #61082 a duplicate

duplicate of bug #54173