Upgrade from Django 1.4 to 1.5 creates South migration
|Reported by:||coolRR||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
I noticed that South suddenly wants to create a new schema migration. I'm guessing that this is due to my upgrade from Django 1.4 to Django 1.5.
The migrations added on_delete=models.SET_NULL, I believe.
I suggest that this become part of the upgrade guide. Better have South create and apply those migrations as quickly as possible after the upgrade, instead of discovering it some time afterwards.