#22831: Migrations should provide a way to 'upgrade' from south via loaddata
-------------------------------+------------------------
Reporter: gcbirzan | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------
People with existing south migrations that contain any kind of data
migrations will need to dump their initial data in a fixture and re-create
it with 1.7 migrations. This is impossible in the current state unless a)
there's an undocumented way to do it, b) one uses mock (or monkey patches
by hand) to change django.core.serializers.python._get_model to the one
from the migration.
The reason that b is needed is because if you modify the model afterwards,
loaddata will explode since the model is different.
Additionally, since migrations are now almost 10 times slower than with
south, nobody will want to create proper data migrations, so this is
really the best way to 'upgrade' from south.
--
Ticket URL: <https://code.djangoproject.com/ticket/22831>
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/051.387b336404d8f4c1aa4387c99b117c06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
