Django 1.7: adding order_by to model Meta class causes Django to create a meaningless migration

[Rob van der Linde]

When you add a Meta class with just an order_by to an existing model, Django 1.7 thinks it needs to create a migration for this change, while this does not change the schema at all and probably shouldn't really require a migration.

South would not create a migration in this case I am pretty sure, it seems Django 1.7 does.

[Baptiste Mispelon]

Hi,

This is by design, as noted in the last paragraph of ​https://docs.djangoproject.com/en/1.7/topics/migrations/#the-commands:

Django will make migrations for any change to your models or fields - even options that don’t affect the database - as the only way it can reconstruct a field correctly is to have all the changes in the history, and you might need those options in some data migrations later on (for example, if you’ve set custom validators).

Thanks.