Bug #37273 | Change order index | ||
---|---|---|---|
Submitted: | 9 Jun 2008 6:58 | Modified: | 1 Jul 2009 10:28 |
Reporter: | Radboud Platvoet | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.0 | OS: | Windows |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | Change order index, CHECKED |
[9 Jun 2008 6:58]
Radboud Platvoet
[9 Jun 2008 10:03]
Johannes Taxacher
verified in 5.0.22
[15 Apr 2009 17:06]
David Finch
Is there a workaround for this, apart from remembering to manually fix the bad ordering in the exported SQL later on (which could be called a workaround for almost every workbench bug ever)? I use compound primary keys to control sorting of records, to group them by their parent record's id.
[15 Apr 2009 19:11]
David Finch
I found my own workaround, which I'll share. Open the .mwb file as a zip file and extract the document.mwb.xml from it. Then open the xml and find object for the table, to get the primaryKey guid. Then search for the primary key's object and rearrange the IndexColumn values within it, and copy the modified xml back to the .mwb zip file.
[30 Jun 2009 18:58]
Johannes Taxacher
fixed in 5.1 now. fix will be included in 5.1.16
[1 Jul 2009 10:28]
Tony Bedford
An entry was added to the 5.1.16 changelog: In the Indexes tab of the Table Editor, it was not possible to change the order number of a column for an index of type PRIMARY in the Index Columns panel, using the drop down list box available in the # column.