Ticket #343 (closed enhancement: fixed)
Ability to force a fake migration to a given state
|Reported by:||anonymous||Owned by:||andrew|
There should be a flag to force a migration to a certain state even if there is a discrepancy between the disk and the database:
! These migrations are in the database but not on disk:
- basic_profiles: 0004_otherusers_change
! I'm not trusting myself; fix this yourself by fiddling
! with the south_migrationhistory table.
The desired result would be that South deletes the record in south_migrationhistory '0004_otherusers_change' without requiring the user to login into the database and 'fiddling' with the table.