Did you ever figure this out? I just upgraded from Django 1.8 to 1.9 and I'm having the same issue.
On Saturday, December 12, 2015 at 10:01:39 PM UTC-8, Xuton Ion wrote: > > Thanks for the assistance so far. > > Reading https://docs.djangoproject.com/en/1.9/topics/migrations/ it says > I should be able to run migrate to apply migrations. > But does this mean I have to manually do something, or should that work > the same as it did on 1.8? > > I am assuming that it should also be able to create the database from the > model with just running that one command. > > When creating a new project the migrate line runs fine, so it seems to be > something specific to the project. I cant share the project though > > On Saturday, 12 December 2015 19:14:55 UTC+2, Tim Graham wrote: >> >> Is there a reason you can't use migrations? --run-syncdb is really only >> meant for huge projects (hundreds or thousands of models) where migrations >> are too slow. Not sure why it's not working though. You'd have to project a >> sample project for me to debug further. >> >> On Saturday, December 12, 2015 at 11:53:37 AM UTC-5, Xuton Ion wrote: >>> >>> No, I haven't added any migrations. >>> >>> I did try with --run-syncdb though, and still had the same error though >>> >>> On Saturday, 12 December 2015 16:26:15 UTC+2, Tim Graham wrote: >>>> >>>> Does your application have migrations? Quoting the 1.9 release notes, >>>> "Automatic syncing of apps without migrations is removed. Migrations are >>>> compulsory for all apps unless you pass the --run-syncdb >>>> <https://docs.djangoproject.com/en/1.9/ref/django-admin/#django-admin-option---run-syncdb> >>>> >>>> option to migrate." >>>> >>>> On Saturday, December 12, 2015 at 8:42:58 AM UTC-5, Xuton Ion wrote: >>>>> >>>>> Hi >>>>> >>>>> I seem to have an issue with running migrate and have been googling >>>>> all day without any luck >>>>> >>>>> I have an app which works and runs on 1.8 >>>>> After cloning the repo and creating a new ve, I ended up with Django >>>>> 1.9 >>>>> >>>>> Running the ./manage.py migrate creates the database, but none of the >>>>> tables from the model. It returns >>>>> django.db.utils.OperationalError: no such table: table_name >>>>> >>>>> If I delete the db.sqlite3 (still in dev so not postgress yet), >>>>> deactivate my ve and use my ve with django 1.8, the migrate line runs >>>>> fine. >>>>> If I then re-activate my ve with 1.9, everything works fine. I can >>>>> make changes and run makemigrations, and it works. But the initial state >>>>> seems to not work >>>>> >>>>> Anyone else have the same issue, or have some advice for me? >>>>> >>>> -- 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 [email protected]. To post to this group, send email to [email protected]. 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/f6542826-440b-403e-97ab-20aad82b1009%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
