#32714: Model meta ordering with nulls_last resulting in constantly needing new
migrations
-------------------------------------+-------------------------------------
Reporter: Kevin Marsh | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"364098fdac597d2293d844d81ab523c22ca5a361" 364098fd]:
{{{
#!CommitTicketReference repository=""
revision="364098fdac597d2293d844d81ab523c22ca5a361"
[3.2.x] Fixed #32714 -- Prevented recreation of migration for
Meta.ordering with OrderBy expressions.
Regression in c8b659430556dca0b2fe27cf2ea0f8290dbafecd.
Thanks Kevin Marsh for the report.
Backport of 96f55ccf798c7592a1203f798a4dffaf173a9263 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32714#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.5a3ddec18a5bf656fd99aac8e09cdae9%40djangoproject.com.
