Column constraints are modified in the incorrect order, resulting in deletion

[cgibbard]

In the case that a diff indicates that a column constraint has been both added and deleted (in particular when a default constraint changes), the migration first adds the new default constraint and then deletes the default constraint, in that order, which results in simply deleting the constraint.

This has the effect that every time a migration occurs, the table alternates between having and lacking the constraint.