Bug #59329 Columns reordering isn't retained using MySQL Workbench
Submitted: 6 Jan 2011 11:05 Modified: 5 Mar 2011 16:43
Reporter: Dominic Harvey Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.31 CE OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[6 Jan 2011 11:05] Dominic Harvey
Description:
When altering table's column ordering using the gui, changes to the table are successfully applied, but new column order doesn't seems to be retained.

How to repeat:
1. using MySQL Workbench SQL Editor, right click on a table and choose "Alter Table...".
2. Go to the Columns Tab
3. change columns ordering by selecting one columns and dragging it into another position in the list.
[6 Jan 2011 18:58] Valeriy Kravchuk
Had you clicked on the Apply button after changing the order?
[6 Jan 2011 19:02] Valeriy Kravchuk
Had you clicked on the Apply button after changing the order?
[6 Jan 2011 19:03] Dominic Harvey
Yes, I did clicked on apply, which bring me to the "Review the SQL Script to be Applied on the Database" page.  And again, I clicked on Apply which indicate that the "SQL scipt was successfully applied to the database".  Unfortunatly, when altering the table again, the columns is still at the same position.
[10 Jan 2011 9:22] Valeriy Kravchuk
What version of server, x.y.z, are you working with? Can you send CREATE TABLE statement for the problematic table and describe what exact re-ordering of columns you had performed?

I can not repeat this with my simple tables on MySQL 5.1.54, thus the requests.
[11 Jan 2011 4:21] Dominic Harvey
Hi, the MySQL server now running version is 5.1.43-community running on Windows 2003 SP2 Standard Edition (English version).

That said, the issue is now resolved.  I believe the latest MySQL Workbench release resolved the issue.

For historical purpose, create Tables and altering any other aspect of tables were working as expected.  The issue were occurring on any tables I had on that server; I want to highlight at the same time that another bug is also no longer occurring, which was related to changing the case of a column name.  The issue was almost the same in the sense that after making modification(s) and applying the changes, MySQL Workbench was report the operation successfully completed, but still not permanently implemanted;  Subsequent table's alteration were still showing columns name with the improper case.

Please feel free to close this case and many thanks for your assistance.
[5 Mar 2011 16:44] Valeriy Kravchuk
Not repeatable with recent Workbench versions.