Erk! My own fault unfortunately, apologies for the noise
Some files had gotten left in a migration folder in an app; causing all sorts of confusion evidently All well now... On Fri, 17 Apr 2015 13:51:08 +0100 Drew Ferguson <d...@afccommercial.co.uk> wrote: > Hi > > Trying to use a legacy database with Django > 1.8 (specifically Django-1.8-py2.py3-none-any.whl with python2.7) > > I followed the steps in > https://docs.djangoproject.com/en/1.8/howto/legacy-databases/ > > i.e. "python manage.py inspectdb" and tidyup the resulting models file > > However when I run "python manage.py migrate" it insists on trying to > create one of the tables; since the table already exists, it crashes > leaving the django tables incorrectly built so I cannot start > django at all i.e. "django_session" does not exist > > In a previous iteration I had django running fine but it always wanted an > "id" field to exist in tables even though there was another field had > "primary_key=True" set > > Is there some trick I am missing or maybe I should not be using 1.8 just > yet > -- Drew Ferguson AFC Commercial http://www.afccommercial.co.uk -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20150417142803.41939d9d%40blacktav.fergiesontour.org. For more options, visit https://groups.google.com/d/optout.
