#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):
Hi, Tim. In my understanding of the problem, we need to accept the
migrations!
Rationale: the way Django serialized the objects before my patch caused
*information loss*. When data was in the database, you could know who was
the parent of a given child (thanks to the `parent_ptr` field), and after
the serialization, you couldn't, because that field was not serialized. So
you need to serialize multi-table inheritance `OneToOneField`s. Since, in
the old code and migrations, these fields had `serialize=False`, that is
just plain wrong! They should be `serialize=True`, so the new migrations
are required. (I assume that, when the field is absent, `True` is assumed,
since the field is not in the new migration.)
So, yes, I think the way to go is to add a release note about it.
What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/27742#comment:5>
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.370da05a6ae8dcf594e3983543b406bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
