Ability to force a fake migration to a given state

[anonymous]

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.

[andrew]

The new option --delete-ghost-migrations was committed in [043f5cd210cc], which I'd say means I can now close the ticket; it's the best solution I could come up with that will work for most people.