#27742: Unexpected migration on Parent -> child model inheritence
---------------------------------+------------------------------------
Reporter: Anthony King | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.11
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Markus Holtermann):
Replying to [comment:6 Anthony King]:
> What are the implications for distributed packages that have parent ->
child models, and intend to support older versions of Django?
Django's version support for migrations is outlined
inhttps://docs.djangoproject.com/en/1.10/topics/migrations/#supporting-
multiple-django-versions . I see how this will lead to errors on 1.11 if
you want to check that all required migrations have been applied. I'll try
to come up with a solution or workaround for your case.
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#comment:7>
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/067.33976d79e0e3acdeaec8c9b08a2ed82c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
