Bug #73644 | "Synchronize with any source" will build buggy script on column rename | ||
---|---|---|---|
Submitted: | 19 Aug 2014 13:49 | Modified: | 13 Nov 2014 1:09 |
Reporter: | Claus Overbeck | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 6.1.7.11891 | OS: | Linux (Ubuntu 14.04 LTS) |
Assigned to: | CPU Architecture: | Any | |
Tags: | column mapping, column rename |
[19 Aug 2014 13:49]
Claus Overbeck
[19 Aug 2014 13:50]
Claus Overbeck
Version 2
Attachment: schema_V2.mwb (application/vnd.mysql-workbench-model, text), 4.85 KiB.
[19 Aug 2014 13:50]
Claus Overbeck
Version 1
Attachment: schema_V1.sql (application/sql, text), 706 bytes.
[19 Aug 2014 14:21]
MySQL Verification Team
Please check with latest release 6.1.7. Thanks.
[19 Aug 2014 15:25]
Claus Overbeck
Also affects current 6.1.7.11891 release
[25 Aug 2014 14:47]
Marcin Szalowicz
Thank you for the bug report.
[13 Nov 2014 1:10]
Philip Olson
Fixed as of the upcoming MySQL Workbench 6.2.4 release, and here's the changelog entry: Exporting an ALTER script using the "Synchronize with Any Source" wizard after making "Column Mapping" (table name) changes would incorrectly generate CHANGE COLUMN queries as "CHANGE COLUMN `newcolumnname` `newcolumnname`" instead of "CHANGE COLUMN `oldcolumnname` `newcolumnname`". Thank you for the bug report.