Bug #55127 SQL_MODE set to
Submitted: 9 Jul 2010 13:38 Modified: 16 Jul 2010 14:40
Reporter: bjorn katuin Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.25 OS:Any
Assigned to: CPU Architecture:Any

[9 Jul 2010 13:38] bjorn katuin 
Description:
all model exports & synchronize actions seem to use

SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

This causes query errors when using an diffrent SQL_MODE on the target server.

How to repeat:
1) create a empty model
2) File > Export > Forward Engineer SQL CREATE Script (Shift + Ctrl + G)

Suggested fix:
set the SQL_MODE to the user define SQL_MODE in
Edit > Preferences > SQL EDITOR > Default SQL_MODE

When not set dont generate SET SQL_MODE statement
[10 Jul 2010 18:30] Valeriy Kravchuk 
Thank you for the bug report.
[12 Jul 2010 2:45] Alfredo Kojima 
Another problem of this SQL_MODE being set is that stuff like default value of 0 for datetime columns will fail.
[16 Jul 2010 14:40] Valeriy Kravchuk 
Actually, this is a duplicate of bug #54173.