#22831: Migrations should provide a way to dumpdata to an initial data migration
-----------------------------+------------------------------------
Reporter: gcbirzan | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => wontfix
Comment:
I don't see what's being asked for here. Django 1.7 and migrations don't
support initial data fixtures, and in addition you're encouraged to do
data migrations using the ORM and RunPython rather than calling loaddata
(I don't want to have to make loaddata take an Apps object to get the
right set of models).
If you have existing South data migrations, you can literally do a find-
and-replace to make the same code work inside RunPython - just exchange
orm['app.Model'] for apps.get_model('app', 'model').
--
Ticket URL: <https://code.djangoproject.com/ticket/22831#comment:4>
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/066.af32eea5f2897990f38827202a05e9c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.