#24537: Migration autodetector not detecting RenameModel if foreign keys are
defined before sibling fields
-----------------------------+------------------------------------
Reporter: rapilabs | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: RenameModel | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c7ec3c07e78e288a48e87b979dbd12e1fa44fe66" c7ec3c0]:
{{{
#!CommitTicketReference repository=""
revision="c7ec3c07e78e288a48e87b979dbd12e1fa44fe66"
Fixed #24537 -- Ignored field order in RenameModel detection
Thanks to David Sanders for the report and test and Simon Charette for
the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24537#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.43f50ab7567f035f478985dc25d91659%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
