Moving from Django 1.6 to 1.8 (relation "django_site" does not exist

[TheBeardedTemplar]

Hello,

I'm trying to move a fairly large site from Django 1.6.5 to Django 1.8.3. I'm also moving from sqlite3 to postgreSQL at the same time and I'm having trouble with the migrations. Here's what I've done so far:

• Installed Django 1.8.3, removed south, and installed psycopg 2.6.1
• Installed postgres admin, and created a new database, then updated settings.DATABASES to connect to it
• Deleted all migration folders from south
• Attempted to run python manage.py migrate (from here I've been messing around trying to get things running)
• Got an error: relation: "scheduler_customevent" does not exist
• Tried making migrations for schedule (and django.scheduler which defines the base class), got "No changes detected in app"
• Tried applying fake migrations for schedule, got "Error creating new content types."
• Tried migrating auth, got relation "django_site" does not exist, with a db error: LINE 1: SELECT (1) AS "a" FROM "django_site" LIMIT 1

At this point I'm kind of floundering - I suspect it might have to do with the name of my schedule app (before I had schedule and django-schedule and that caused trouble in 1.8, so I renamed mine to scheduler).

I'd appreciate some guidance on where to go next - it seems like I'll really benefit from the migration system in 1.8, I just need to understand it first.

Thanks!

[Gary Roach]

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/afa49126-c6ae-4bdf-a677-38c2b7ea5969%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Not sure this will help or is even relevant but there is a significant difference in the settings.py file  between the two versions. Specifically, the inclusion of a templates tuple. Check the files carefully for differences.

Gary R

[TheBeardedTemplar]

Thanks for the settings.py suggestion Gary - I did make various changes there prior to this post. I ended up resolving the issue by running makemigrations for every app individually, then migrating.

Unfortunately I'm now running into trouble with my tests - I'm hitting the same errors for my test database.