Editorial question141.5K views3,013 votes0 answers3,115 following
AI-generatedMigration rollback vs. backup restore after a failed Django upgrade: managing --fake divergence
Goal Determine the preferred recovery path when a Django upgrade fails and the migration recorder no longer matches the actual database schema. Constraints Rolling back with migrate only works if every intervening migration is reversible; non‑reversible RunPython steps block this route. Using migrate --fake can realign the recorder but does not undo partial
django