makemigrations when adding field with a unique_together constraint should create fields before constraints

[Chris Beaven]

Added a slug field to a Tag model, and a unique_together constraint of [('site', 'slug')]

Running makemigrations resulted in a migration with the operations ordered like this:

    operations = [
        migrations.AlterUniqueTogether(
            name='tag',
            unique_together=set([(u'site', u'slug')]),
        ),
        migrations.AddField(
            model_name='tag',
            name='slug',
            field=models.SlugField(default=''),
            preserve_default=False,
        ),
        migrations.AlterField(
            model_name='tag',
            name='name',
            field=models.CharField(max_length=20),
        ),
    ]

That choked when running the migration, but manually changing the constraint to happen after the field addition worked fine. Apart from the fact that I should probably have made this two migrations, would it be sensible to order the AlterUniqueTogether operations last?

[Anton Baklanov]

I can confirm this on current master.
Will try to write test+patch for this now.

[Anton Baklanov]

​pull request

[Tim Graham <timograham@…>]

In 0bd92d68ade11b56124c7cdfbbfff6eb37899291:

Fixed #22035 -- reordered migration operations

Now AddField actions appear in operations list before AlterUniqueTogether
actions.

Thanks to SmileyChris for the report.