Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Django Migrations Broken
See original GitHub issue#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:
python manage.py migrate social_auth 0004 --fake
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to solve broken migration history in Django - Dev Genius
How to solve broken migration history in Django · 1. Export all data from that table · 2. Migrate app_name zero · 3....
Read more >Django: broken migrations - python - Stack Overflow
I am trying to setup a Django app locally in a new machine but migrations seem to be totally broken. They need to...
Read more >Detecting code that will break Django migrations
This will happen when setting up a new database when all the migrations run from scratch such as in the CI, when a...
Read more >How to Reset Migrations - Simple is Better Than Complex
1. Make sure your models fits the current database schema · 2. Clear the migration history for each app · 3. Remove the...
Read more >Django: Handling broken migrations - Abu Ashraf Masnun
Often for one reason or another, migrations don't apply properly and we have to fix them manually. If there's a faulty migration that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Noting that fixtures with
"default.usersocialauth"need to be manually updated to"social_auth.usersocialauth"as well.@omab thank you!