#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 Tim Graham):
I'm still not convinced that the fix for #24607 is ideal. It also marks a
`OneToOneField` that's a primary key of a model (non-multi-table
inheritance) as `serialize=True` which doesn't seem desirable or
necessary. If a better fix for that ticket can't be developed by Feb. 20
(1.11 beta), I'm thinking to revert it.
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#comment:8>
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.6b573ff19e1f792108aeb66ec03a5c7e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
