FieldDoesNotExist error in migration with deleted fields and unique_together constraint

[Nico Benitez]

I had a model that had a ForeignKey field and a unique_together constraint involving that field. I deleted both the field and the unique_together constraint in my model and ran makemigrations. The migration created RemoveField operation and a AlterUniqueTogether operation with unique_together=set([]). When I tried to run the migration, a django.db.models.fields.FieldDoesNotExist exception occured. I edited the migration manually to put the AlterUniqueTogether operation before the RemoveField operation and then the migration worked.

NOTE: After upgrading, you must remove the bad migration file and re-run makemigrations or manually move the AlterUniqueTogether operation manually as stated above; i.e. upgrading does not fix the existing migration.

[Simon Charette]

Managed to reproduce against master.

[Simon Charette]

Pull-request submitted at ​https://github.com/django/django/pull/3533

[Tim Graham <timograham@…>]

In 72729f844e0dd9bd01b3874171b89ab0d136a40e:

Fixed #23794 -- Fixed migrations crash when removing a field that's part of index/unique_together.

[Tim Graham <timograham@…>]

In feded19104b14bc28aaccf550265157df84593ba:

[1.7.x] Fixed #23794 -- Fixed migrations crash when removing a field that's part of index/unique_together.

Backport of 72729f844e0dd9bd01b3874171b89ab0d136a40e from master