#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 Anthony King):
What are the implications for distributed packages that have parent ->
child models, and intend to support older versions of Django?
We currently have a testCase at work to ensure all migrations have been
generated. This test would fail if we were on Django 1.10, and the library
had the serialize migration applied in Django 1.11 (or vice-versa).
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#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 [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.b111c40e1ca8429d2d5d173012bad032%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
