#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 João Paulo Melo de Sampaio):
Hmm, I understand your point now. Then the change required is not needed
at the models level, but at the serializer level. The serializer must
treat those O2OPK fields differently whether natural primary keys are
enabled or not. I agree that my patch must be reverted.
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#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 [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.f449dd54594ec29ad3d4cbb8fa4f2053%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
