#21830: dumpdata: option to fetch related objects
-------------------------------------+-------------------------------------
Reporter: stanislas.guerra@… | Owner: nobody
Type: New feature | Status: closed
Component: Core | Version: master
(Serialization) | Resolution: duplicate
Severity: Normal | Triage Stage:
Keywords: dumpdata | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by russellm):
What you're missing is that you're only providing a solution for one, very
specific subset of problems, whereas serialisation is a lot more complex
than that. What I'm wary of is changing the serialisation format in a way
that only solves a very small subset of problems, because every API we add
means another feature we need to maintain backwards compatibility with
when we *do* get around to fixing serialisation.
Django's current serializers are sufficient to do a dump and reload. If
you want to fix dependency evaluation, a patch providing a flag that tells
the serializer to unroll model dependencies, but uses the existing format,
would be a lot more likely to get accepted, IMHO. However, as you note,
there are all sorts of limitations related to ordering, etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/21830#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/084.6216568a7b10dc92e0d83e57e307d04a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
