RenameField after AddField after CreateModel in one operations list gives ProgrammingError: relation "field" does not exist

[Matthew Pava]

In one migration file, I have this series of operations:

migrations.CreateModel(m, fields=[a, b, c])
migrations.AddField(m, x)
migrations.RenameField(x, y)

I get this:

 ProgrammingError: column "x_id" does not exist.

I workaround it by replacing x with y in the AddField operation and then removing the RenameField operation.

[Tim Graham]

Can you test with Django 2.0?

[Matthew Pava]

Not at the moment with my particular project, though I have tried. (I'm waiting for a 3rd-party package to get Django 2.0 support.) I will continue trying tomorrow, but I will state that I'm getting different results than with Django 1.11. There are still some bugs I'm seeing, but I haven't determined conclusively if they are related to the migrations.

[Simon Charette]

If you get the ProgrammingError during index or foreign key constraint creation than I'm fairly confident this is a duplicate of #25530 which is fixed in Django 2.0.

[Tim Graham]

Please reopen, if needed.

[Matthew Pava]

For clarification purposes, this bug has been fixed in Django 2.0.