Opened 6 years ago

Closed 6 years ago

#28916 closed Bug (duplicate)

Changing the type of a ForeignKey and changing unique_together creates migrations in the wrong order, causing migrations to fail

Reported by: fredley Owned by:
Component: Migrations Version: 2.0
Severity: Normal Keywords: migrations
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by fredley) before:

class MyModel(models.Model):
    fka = models.ForeignKey(SomethingA, ...)
    date = models.DateField()

    class Meta:
        unique_together = ('fka', 'date') after:

class MyModel(models.Model):
    fkb = models.ForeignKey(SomethingB, ...)
    date = models.DateField()

    class Meta:
        unique_together = ('fkb', 'date')

This can result in an automatically created migration (using makemigrations) that looks like this:

operations = [
        field=models.ForeignKey(... to='myapp.somethingb'),
        unique_together={('fkb', 'date')},

This migration fails, because AlterUniqueTogether needs to come before RemoveField, as it references fka. This is hard to debug, and can only be fixed by manually reordering the migration operations.

Change History (5)

comment:1 by fredley, 6 years ago

Component: UncategorizedMigrations

comment:2 by fredley, 6 years ago

Description: modified (diff)

comment:3 by Junji Wei, 6 years ago

Owner: changed from nobody to Junji Wei
Status: newassigned

comment:4 by Junji Wei, 6 years ago

Owner: Junji Wei removed
Status: assignednew

comment:5 by Ramiro Morales, 6 years ago

Resolution: duplicate
Status: newclosed

I think this is a duplicate of #28862.

Note: See TracTickets for help on using tickets.
Back to Top