#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
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => wontfix
Comment:
> At first glance, using `manage.py dumpdata` and `loaddata` together
seems a great way to make a full copy of an existing django installation
(e.g. for migrating to a different server, or getting a local copy of your
production data, etc.). Documentation suggests this should be possible.
I don't see such suggestions in docs. Given that `dumpdata` isn't meant
as a backup tool (databases have their own tool for that), I think should
not add more options to make it easier or to document a more or less
feasible scenario.
--
Ticket URL: <https://code.djangoproject.com/ticket/31869#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.b03fdc3b78f4349eab66a4b1e598ea0f%40djangoproject.com.
