On Saturday 18 March 2017 08:52:03 Andréas Kühne wrote: > You shouldn't get any errors when running migrations. What I am > guessing now is that the sessions table is missing completely or some > of the columns in the table are missing.
But you would only be in that state, if the session migrations are in django_migrations and the tables removed afterwards. So clearing the django_migrations table from entries with app='sessions' should recreate them, but you may get inconsistent history errors. It's generally not pretty to use migrations and then hack the database. If you use migrations to alter your schema, you should always use migrations or be prepared to jump down the rabbit hole. -- Melvyn Sopacua -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2920523.2ZJsQo3oRE%40devstation. For more options, visit https://groups.google.com/d/optout.
