#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):
Tim, you said that the `OneToOneField` that is also a primary key (and, in
Django's solution to this, relates the parent and the child) should not be
serialized. How do you suggest we relate the parent and the child in a
pool of instances of the parent class and instances of the child class?
There's no way to relate them if we don't know their primary keys.
Reverting this, we go back to a state that exporting multi-table
inheritance models with `dumpdata` incurs in loss of information.
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#comment:9>
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.2026c0fdcd04254bb42ce2b9f90e9ff3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
