7

I have created a model and executed syncdb which had created the tables as my model was designed.
Afterwards I modified the model and executed makemigrations which created the migrations ignoring the tables that syncdb had already created.

So I ended up with an error "relation already exists".

Why did makemigrations created everything from scratch? How do I fix this situation ?

Aymane Shuichi
  • 460
  • 5
  • 14
  • Try `python manage.py migrate --fake `. – Rahul Gupta Aug 30 '15 at 18:00
  • For some reason it doesn't apply the new changes . I have read somewhere that the migration is marked as done in django_migrations database. Anyways I solved the problem and I just found out that the're going to remove syncdb from django 1.9 – Aymane Shuichi Aug 30 '15 at 18:06
  • Yes, it was deprecated from Django 1.7 and will be removed in Django 1.9 . – Rahul Gupta Aug 30 '15 at 18:08

2 Answers2

13

makemigrations creates new migrations based on the changes detected to your models.

Also, one thing to note is syncdb command is deprecated since Django 1.7 and will be removed in Django 1.9. So, you should use the migrate command.

From syncdb docs:

Deprecated since version 1.7:
This command has been deprecated in favor of the migrate command, which performs both the old behavior as well as executing migrations.

Rahul Gupta
  • 46,769
  • 10
  • 112
  • 126
2

makemigration always creates one migration file having all the changes. So, when you run makemigration for first time it tries to find the previous migration file. if not found it creates one initial migration file. And when it tries to apply it to the db it finds the relation already exists. And thus throws error. Best practice is, before updating model, create one migration then modify the model.

Amrendra
  • 511
  • 8
  • 18