﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
32714	Model meta ordering with nulls_last resulting in constantly needing new migrations	Kevin Marsh	Simon Charette	"Just upgraded from Django 3.2. to 3.2.1 and now `makemigrations` always shows the same change. The issue seems to be if you have:

{{{
class SampleModel(models.Model):

    name = models.CharField(null=True, max_length=255)

    class Meta:
        ordering = [F('name').asc(nulls_last=True)]

}}}
Running `makemigrations` always results in the ordering changing for `SampleModel`, think maybe this was introduced when trying to solve #32632 since for:
{{{
a = F('name').asc(nulls_last=True)
b = F('name').asc(nulls_last=True)
}}}
In Django 3.2 `a == b` but in Django 3.2.1 `a != b`"	Bug	closed	Migrations	3.2	Release blocker	fixed		Johannes Maron	Ready for checkin	1	0	0	0	0	0
