#24778: Data Migration from Fixture
-----------------------------+-----------------------------------------
Reporter: 9gix | Owner: vccabral
Type: New feature | Status: assigned
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 MarkusH):
As mentioned above in comments 3 to 5 and suggested by charettes, the
"right" approach to this issue is likely adding `apps` as an optional
argument to the serializers and using that in a next step.
A command that dumps a fixture file or a database as a database migrations
feels ugly here. You're essentially creating (arbitrary) python code that
follows absolutely no patterns (how do you handle multi line strings, byte
strings, UUIDs, ...)?
--
Ticket URL: <https://code.djangoproject.com/ticket/24778#comment:10>
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.19e78dc195ccf0dbf9cee11eaad473bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
