[Answered ]-Django superuser fixture error โ€“ no such table: auth_user

2๐Ÿ‘

โœ…

I solved my problem, however it is definitely not the prettiest solution.

I saw that when I run heroku run python manage.py syncdb, I get the following

Operations to perform:
  Synchronize unmigrated apps: myproject, permissions, myapp1, myapp2
  Apply all migrations: auth, flatpages, admin, contenttypes, sessions, sites
Synchronizing apps without migrations:
  Creating tables...
    Creating table app1_model1
    Creating table app1_model2
    ...

So I thought what if i migrate the included apps in reverse order :

heroku run python manage.py migrate sites; heroku run python manage.py migrate sessions; heroku run python manage.py migrate contenttypes; heroku run python manage.py migrate admin; heroku run python manage.py migrate flatpages; heroku run python manage.py migrate auth;

and it worked! I have no idea why, but it did. Maybe this will help someone else too.

๐Ÿ‘คjeff

Leave a comment