#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 felixxm):
> Apologies if I come across stubborn, but I feel that just saying "This
is unsupported" is insufficient in this case. Maybe this is extra annoying
because I'm not the first one to suggest this and this is a repeating
discussion for you, but if so that would be even more indication that this
usecase should be better documented (even if just as not supported).
We cannot document each unsupported scenario. It's also
[https://docs.djangoproject.com/en/3.1/topics/serialization/#natural-keys
documented] that ''"You should never include automatically generated
objects in a fixture or other serialized data."''
> This does not seem like a weird or unconventional usecase to me.
Moving data between different databases is always hard, because you can
encounter multiple issues e.g. inconsistent or non-existent data types,
and much more (that's why we have many feature flags). Adding support for
overriding and existing and not empty instance with `loaddata` and
`dumpdate` is really complicated, and IMO we shouldn't officially support
it.
> What defines the line between supported and not supported?
If sth is not tested and documented then it's not supported.
You can start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/31869#comment:6>
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.caed4cab6b755da32da7e2a675b95983%40djangoproject.com.
