propelorm/Propel2 — Issue #20: Provide a build option to sort all info in the schema.xml from the 'reverse' task so that the xml structure is always in guaranteed order
Author: apinstein
Created: 2011-10-21 14:44:36+00:00
State: open

Migrated from: https://github.com/propelorm/Propel/issues/149

Right now the schema.xml is ordered by when a table/column/index/etc is added to the schema, not alpha order. Well, actually table entries are alpha, but I think that's coincidence.

The problem is that if multiple people work on the DB at the same time, their changes may cause the "reverse" task to generate "changes" to the schema file that don't actually exist. This makes changesets larger than they have to be and adds risk to committing re-built code.

I propose that a new build option be added that allows you to have the reverse task sort all entries alphabetically so that the order of the schema can be counted on to be the same for an "equivalent" database.

I will write this code and submit a patch shortly.