Bug #61720 | Model to DB Synchronization appears to not pull default values from db | ||
---|---|---|---|
Submitted: | 1 Jul 2011 16:21 | Modified: | 4 Sep 2012 21:04 |
Reporter: | Csaba Skultety | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.34 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[1 Jul 2011 16:21]
Csaba Skultety
[1 Jul 2011 17:34]
Valeriy Kravchuk
What exact version of server, x.y.z, are you working with?
[1 Jul 2011 18:05]
Csaba Skultety
5.1.41 server running on Windows and it also does it with 5.1.49 server running on ubuntu
[3 Jul 2011 1:44]
MySQL Verification Team
Thank you for the bug report.
[4 Sep 2012 21:04]
Philip Olson
Fixed as of the upcoming 5.2.44, and here's the changelog entry: When synchronizing a model to a database after changing a field definition from "NOT NULL DEFAULT x" to "NULL DEFAULT NULL", the model synchronization would correctly generate the SQL. But after executing this SQL and resynchronizing, MySQL Workbench would report that the table needed to be updated. Thank you for the report.