Closed clintonb closed 8 years ago
It may also be possible to use the replaces
functionality normally reserved for squashed migrations.
FYI @omab @cclay
@omab would you mind releasing v0.2.21 with this change?
@rlucioni , v0.2.21
released
@omab thank you!
Noting that fixtures with "default.usersocialauth"
need to be manually updated to "social_auth.usersocialauth"
as well.
916 changed the app name from "default" to "social_auth". Users running the app prior this change will have migrations registered under the old name, resulting in Django thinking it should apply migrations from scratch.
These existing migrations should be faked with the following command: