#31869: Improving data migration using `dumpdata` and `loaddata`
-------------------------------------+-------------------------------------
Reporter: Matthijs Kooijman | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: 3.1
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Matthijs Kooijman):
> I don't see such suggestions in docs.
This is not explicit, but IMHO implied. There's a command to make a dump
of the data for all applications, and there's a command that can load such
dumps, which suggests to me that I can use this to make a copy of all my
data into another django instance. If not, maybe this should be made
explicit in the docs.
> Given that dumpdata isn't meant as a backup tool (databases have their
own tool for that)
I was not talking about backups here (I agree that database-specific tools
are better for this, though I could also see `dumpdata` as a second-best
option), but about copying data from one instance to another. But that's
just a matter of definition, I'm assuming that you would also consider
that dumpdata is not meant for such data copying?
If so, then what is `dumpdata` meant for exactly? Is it only for creating
test fixtures? Then why does it have a "dump all applications" option
and/or why does it include contenttypes and other autogenerated data at
all (even by default)?
And even if this copying is not the intention of `dumpdata`, is there any
reason that its intended usecase cannot be expanded to include this? It
seems to me that it would be easy to do so, but maybe there are
fundamental issues or things that prevent this from working reliably? If
so, maybe it would be better to document that fact (maybe with some
examples) to make this more explicit and correct user expectations. If you
can point out things here, I'd be happy to submit a documentation PR for
this.
--
Ticket URL: <https://code.djangoproject.com/ticket/31869#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.b2cb918e955c583bb79d4ffaa8847a3a%40djangoproject.com.
