#28493: Foreign keys break on migration if models are renamed in a different app
-------------------------------------+-------------------------------------
Reporter: Christopher | Owner: Jeremy
Neugebauer | Satterfield
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0891503fad458e7dfabc5adbf314f80e78e63f14" 0891503f]:
{{{
#!CommitTicketReference repository=""
revision="0891503fad458e7dfabc5adbf314f80e78e63f14"
Fixed #28493 -- Made migrations autodetector find dependencies for model
renaming.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28493#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.764e40fa91db717a8c2ddfe350adfe47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
