Bug #68489 | Error synchronizing model with table having rows with date set to 0000-00-00 00: | ||
---|---|---|---|
Submitted: | 25 Feb 2013 20:14 | Modified: | 26 May 2013 17:07 |
Reporter: | Artur Stępień | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.44 revision 9933, 5.2.47 revision 10398 | OS: | Windows (Windows 7 x64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | SQL_MODE, synchronization |
[25 Feb 2013 20:14]
Artur Stępień
[25 Feb 2013 20:43]
MySQL Verification Team
Please provide your project modl file (private if you wish). Thanks.
[28 Feb 2013 14:42]
Artur Stępień
Latest build is also affected. What I did found is that that error is because SQL_MODE in Preferences (default SQL_MODE) is set to: TRADITIONAL,ALLOW_INVALID_DATES When it is set like this. Server will reject update. Removing TRADITIONAL helps. Also, in new Workbench version there is per connection SQL_MODE but it is ignored. Whatever is set there it is not used in queries (Instead default SQL_MODE is used). It also should be fixed in future release.
[26 Mar 2013 16:52]
Armando Lopez Valencia
Thanks a lot for your report. Verified in: Windows 7x64 WB 5.2.47 Only one SQLMODE value is accepted.
[26 May 2013 17:07]
Alfredo Kojima
Duplicate of bug #59868