#35251: dumpdata refactoring
-------------------------------------+-------------------------------------
Reporter: Hovi | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core | Version: 5.0
(Management commands) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As far as I know, there is not more granular control over dumping database
fixtures.
I need to create fixtures in a more controlled fashion so I will do my own
management command, I basically gotta copy-paste whole dumpdata management
commant code and then modify relatively small part of it while keeping the
rest the same.
The main logic of `dumpdata` it is directly in `handle` method, which
makes it impossible to reuse. I'd like to refactor contents of this method
into smaller methods so that I can reuse some of it and make it easier to
use dumping functionality.
Is that something that would be welcome?
--
Ticket URL: <https://code.djangoproject.com/ticket/35251>
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/0107018ddf221b4c-8dd354ae-5f7d-4aaa-821a-5b0194c461ea-000000%40eu-central-1.amazonses.com.
