django: by mistake deleted migration files from production server

Question

By mistake I deleted all the migration files from all apps on production server.

Now running python manage.py makemigrations and then python manage.py migrate raises:

"field already exists in the database"

error for each field, What should I do ?
django version: 1.7.7

If your migrations are all auto generated, then you don't need to run `migrate` anymore. Just run `makemigrations` and leave the migration file there. I think you might consider using version controls like `git` to track all files, so you don't lose anything. — Shang Wang, Aug 13 '15 at 17:43
Your code is all in version control, right? Just check out the latest version again and redeploy. — Daniel Roseman, Aug 13 '15 at 17:56

score 0 · Answer 1 · answered Aug 13 '15 at 20:02

0

If you already migrated and then deleted.Then fake will help you

python manage.py migrate --fake

answered Aug 13 '15 at 20:02

itzMEonTV

score 0 · Answer 2 · answered Aug 13 '15 at 20:50

0

you have to fake the migration, the next command may help you:

python manage.py migrate 'name_app' 'name_migration' --fake

Example:

python manage.py migrate books 005_auto_20150505 --fake

answered Aug 13 '15 at 20:50

Hetdev

2 Answers2