#33510: dumpdata command misses models sublcassed from other non-abstract models
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
robinharms |
Type: Bug | Status: new
Component: Core | Version: 3.2
(Management commands) |
Severity: Normal | Keywords: dumpdata
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Essentially the same issue that was fixed in Django 2 has resurfaced in 3
so I'll only write a short description.
{{{
class Person(models.Model):
some_field...
...
class Doctor(Person):
doctor_field...
...
my_doctor = Doctor.objects.create(...)
}}}
Running manage dumpdata will cause the export to be broken. The
"my_doctor" instance will be exported without the pointer to the person-
object it will models will be within the export, but without the linking
pointer value. (Probably called something like person_ptr) However if
--natural-primary is included, the key will be there.
However, regardless of method the needed linked data within the person
table is omitted, so running import data on a site with subclassed models
like this will ''never'' work.
This bug seems to be present in 3.0 and onward.
--
Ticket URL: <https://code.djangoproject.com/ticket/33510>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.fbc5f79a3d7de25877b2ca2fe1aa324e%40djangoproject.com.
