#31869: Improving data migration using `dumpdata` and `loaddata`
-------------------------------------+-------------------------------------
Reporter: Matthijs Kooijman | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: 3.1
commands) |
Severity: Normal | Resolution:
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):
Just realized that I forgot to list one option, which I think is the most
practical way to do this right now:
- Instead of using `manage.py flush`, use a database-specific management
tool (e.g. phpmyadmin) to empty/truncate all tables *except* for
migrations. Then just use `dumpdata` and `loaddata`, which should get you
an identical import, including identical primary keys. This works, but
still requires external tools, so is harder to quickly do and/or automate,
so a `manage.py`-only solution would certainly be nicer.
--
Ticket URL: <https://code.djangoproject.com/ticket/31869#comment:1>
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.e30d2a8f3936853144560160efe2f20c%40djangoproject.com.
