2
Django 1.8.15 for project_2/. I’ve just checked project_1/ django version and it is 1.6. I was convinced that both projects where using the same django version.. Is this the main problem?
Yes. Because django 1.6 and django 1.8 use different syncdb commands. syncdb in 1.8 is migrate, so when you do syncdb in 1.8 you are applying migrations, not just creating tables. Use same django version and problem should be solved.
3
You can open the migrations file and comment out the SQL that tries to create the table.
Then run migrations again.
(another possibility would be to delete the table in the database, but you’d lose the data in the table.)
1
If you use django version >1.7 you should use migrations (Django Migrations – make sure to check version matches yours)
Then you can make migrations more consistently (no conflicts). Even if they happen (but under very specific conditions), you can always ‘–fake’ migrations on second host
- [Django]-Exception while installing packages in Python
- [Django]-Django haystack doesn't add to Solr index. [Works with whoosh, fails with Solr]