Index columns in generated SQL are incorrectly ordered by when they were first input rather than where they are currently located, causing errors

The SQL that is generated orders columns for indexes by when they were first input into the table, rather than how they currently appear in the diagram. This causes malformed indexes and errors when running the queries. For example, this FK:

KEY `FK_idx_account_profile` (`profileNum`, `accountID`),
CONSTRAINT `FK_account_profile` FOREIGN KEY `FK_account_profile` (`profileNum`, `accountID`) REFERENCES `profile` (`profileNum`, `accountID`)

Should be as specified by the diagram like so:

KEY `FK_idx_account_profile` (`accountID`, `profileNum`),
CONSTRAINT `FK_account_profile` FOREIGN KEY `FK_account_profile` (`accountID`, `profileNum`) REFERENCES `profile` (`accountID`, `profileNum`)

To reproduce:

1. Create a new table with a compound primary key composed of two or more columns

2. Re-order the columns by dragging one above the other

2. Create a second table and a relationship from the first table to the second table

3. Generate SQL

ACTUAL: columns for index appear in the order input, causing a mismatch with primary key

EXPECTED: columns appear in the order currently displayed in diagram, matching primary key

The workaround is to delete the columns from the diagram then re-insert them in the order you would like them to appear in the SQL.