2👍
✅
This is assuming you are using South 0.8 or so and Django 1.6 or below:
I can’t explain why this happened without knowing more about the history of your database and South usage, but to help in diagnosing the issue you could manually inspect the South migration history table in your database.
However, whatever you find out, the remedy is likely to be the same: you can “fake” the migration and skip ahead to the proper place in your migration history.
Try python manage.py migrate banks 0037 --fake
. That will take you to just BEFORE the 0038
migration without actually trying to create tables. Of course, this assumes that 0037
is the most recent migration that was successfully applied to your database.
Source:stackexchange.com