Migrations should provide a way to dumpdata to an initial data migration
|Reported by:||gcbirzan||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.
Change History (6)
comment:1 Changed 2 years ago by
|Patch needs improvement:||unset|
|Summary:||Migrations should provide a way to 'upgrade' from south via loaddata → Migrations should provide a way to dumpdata to an initial data migration|
|Triage Stage:||Unreviewed → Accepted|
|Type:||Uncategorized → New feature|
|Version:||1.7-beta-2 → master|