Ticket #576 (closed defect: duplicate)
South incorrectly orders primary_key alterations in backwards()
|Reported by:||anonymous||Owned by:||andrew|
I was moving from using a OneToOneField? as a primary key to having an auto-managed primary key. South generated code in backwards() that added the old OneToOneField? primary_key before removing the new auto-managed id field, causing an error on running that complained about having multiple primary keys.