#24778: Data Migration from Fixture
-----------------------------+-----------------------------------------
Reporter: 9gix | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Someday/Maybe
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------+-----------------------------------------
Comment (by vccabral):
I ran into the app state not matching the model.py state while loading
fixtures and ended up creating a branch of django to handle this use case.
I issued a PR to a feature branch in my fork of django. I am more than
willing to work on this issue given the appropriate guidance. I will
finish up reading the contributor guidelines.
https://github.com/vccabral/django/pull/2
--
Ticket URL: <https://code.djangoproject.com/ticket/24778#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.4122fdaad916e30560ddda49b3423286%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.