Propel diff task does not honor column order on MySQL

[Shyru]

When new columns are added to a table from one version to the other, the propel migration will add all columns to the end of the table.
For MySQL this is fixable, because MySQL supports an ALTER TABLE ADD COLUMN abc AFTER Xy Syntax.
I fixed this by reimplementing getAddColumnDDL() and getAddColumnsDDL() in MysqlPlatform.
Pull request incoming...

[Shyru]

Here is the link to the pull-request implementing a fix:
#275

[fzaninotto]

Respecting the XML order in the SQL migrations is not a requirement, since Propel always asks for columns explicitly in every request.

That being said, if you need to have the same columns in XML and SQL, you can always edit the generated migrations before executing them.

[Shyru]

For us it is a requirement, as we use the column order to automatically generate forms to edit models. So for us its important to have the correct order. And when we have to rewrite all migrations by hand this feature is not of great use for us.
So you tell me that we have to apply this patch every time we update Propel?

[nihongomaster]

This fails when attempting to use a custom query/prepared statement.

If by doing SELECT * FROM

WHERE <table.id> NOT IN (SUBSELECT)

And then using a formatter to format it into objects, the column order is wrong, therefore it breaks.

This needs to be reopen to handle this edge case.