#35424: Migration autodetector fails when order_with_respect_to is removed, but
an
_order field remains
-------------------------------------+-------------------------------------
Reporter: Stuart Attenborrow | Owner: Daniel
| Patrick
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | 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
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"d12184fedcd586e2c399ea40abe4bf865ebc87a6" d12184fe]:
{{{#!CommitTicketReference repository=""
revision="d12184fedcd586e2c399ea40abe4bf865ebc87a6"
Fixed #35424 -- Checked order_with_respect_to is available when migrating
_order fields.
Migrations would crash following the removal of an order_with_respect_to
field from a model and the addition of an _order field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35424#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701909b5fa86d-0dccc17b-a974-4f08-81bf-fdc31140997d-000000%40eu-central-1.amazonses.com.
