Infinte migrations when changing Meta options

[JockeTF]

Changing a model's meta options sometimes causes Django to generate an infinite number of migrations.

Create a model with meta options.

from django.db import models

class Pony(models.Model):
    date_created = models.DateTimeField()

    class Meta():
        ordering = ('-date_created',)

Make migrations.

$ python3 manage.py makemigrations
Migrations for 'infinite':
  0001_initial.py:
    - Create model Pony

Remove the meta options from the model.

from django.db import models

class Pony(models.Model):
    date_created = models.DateTimeField()

Make migrations.

$ python3 manage.py makemigrations
Migrations for 'infinite':
  0002_auto_20140728_1440.py:
    - Change Meta options on pony

$ python3 manage.py makemigrations
Migrations for 'infinite':
  0003_auto_20140728_1440.py:
    - Change Meta options on pony

$ python3 manage.py makemigrations
Migrations for 'infinite':
  0004_auto_20140728_1440.py:
    - Change Meta options on pony

I first encountered this issue when upgrading from Django 1.7b4 to 1.7c1. I do not know what exactly is causing this, but it happens in more cases than just when removing the meta options. In my project I have many migrations scripts for several different models. Two of the models ended up suffering from this issue after upgrading to Django 1.7c1. The issue is still present in Django 1.7c2. Squashing the migrations does not help. However, removing the migrations and starting anew solves the issue.

Below is an example of a squashed migration which suffers from this issue.

from django.db import models, migrations

class Migration(migrations.Migration):

    replaces = [('infinite', '0001_initial'), ('infinite', '0002_auto_20140728_1440')]

    dependencies = [
    ]

    operations = [
        migrations.CreateModel(
            name='Pony',
            fields=[
                ('id', models.AutoField(serialize=False, auto_created=True, primary_key=True, verbose_name='ID')),
                ('date_created', models.DateTimeField()),
            ],
            options={
                'ordering': ('-date_created',),
            },
            bases=(models.Model,),
        ),
        migrations.AlterModelOptions(
            name='pony',
            options={},
        ),
    ]

Starting from scratch solves the issue.

from django.db import models, migrations

class Migration(migrations.Migration):

    dependencies = [
    ]

    operations = [
        migrations.CreateModel(
            name='Pony',
            fields=[
                ('id', models.AutoField(primary_key=True, serialize=False, auto_created=True, verbose_name='ID')),
                ('date_created', models.DateTimeField()),
            ],
            options={
            },
            bases=(models.Model,),
        ),
    ]

[Tim Graham]

I can reproduce.

[Andrew Godwin <andrew@…>]

In d6e73a876d77e889efe839345d39690a7004e2f4:

Fixed #23121: AlterModelOptions operation not changing state right

[Andrew Godwin <andrew@…>]

In 394053ce605a30c742d6270a80986b255adb3a30:

[1.7.x] Fixed #23121: AlterModelOptions operation not changing state right

[JockeTF]

Thank you! I can confirm that this solves the issue.

[bacilla]

The same bug in version 2.1. Test project in attachment.

Migrations log:

$ python manage.py makemigrations app
Migrations for 'app':
  app/migrations/0001_initial.py
    - Create model TestEntity
$ python manage.py makemigrations app
Migrations for 'app':
  app/migrations/0002_auto_20180907_1712.py
    - Change Meta options on testentity
$ python manage.py makemigrations app
Migrations for 'app':
  app/migrations/0003_auto_20180907_1713.py
    - Change Meta options on testentity
$ python manage.py makemigrations app
Migrations for 'app':
  app/migrations/0004_auto_20180907_1713.py
    - Change Meta options on testentity

[bacilla]

test project

[Simon Charette]

Please open a new ticket instead of re-opening this closed one.

The issue you're encountering is due to a bug in a new feature in 2.0 that allowed expressions to be used in Model.Meta.ordering (#26257) and has little to do with this Django 1.7 era bug.