#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 stanislas.guerra@…):
Replying to [comment:1 russellm]:
> Improving Django's serialisation is a task that has been proposed a
number of times, and has been the subject of at least one Summer of Code
project, and a number of unsuccessful SoC applications.
>
> I strongly advise that if you're planning this to be integrated into
trunk, you spend some time discussing your proposal on django-dev, because
what you've proposed here isn't likely to get far. Look through the
mailing list archives for more details, but in short, I don't think you'll
get a lot of support for adding small features to the existing serializer.
What is needed is a genuinely configurable serialisation approach,
allowing configuration of serialization depth, format, key naming, and so
on. We need to solve the *whole* problem, not just address a very specific
subset of the problem that you're currently experiencing.
>
> For administrative purposes, I'm comfortable calling this a duplicate of
#4656 (since what you're talking about here is a depth=1 subset of the
functionality described in that ticket).
Hi Russelm,
Well, this is not really a duplicate of #4656 since the proposed patch
does not care about ''depth''. You can traverse one relation with two
levels of depth and another one with five and so on in the same command.
Is it not a common problem when one need to build some fixtures of test -
without dumping/loading the whole database or manually picking each
dependency - that can't be fixed without ''rethinking the whole thing''?
Or maybe I am missing an existing/obvious solution?
--
Ticket URL: <https://code.djangoproject.com/ticket/21830#comment:2>
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.1ea3f759315437ee559b2e34383c6409%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
