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 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/1e3e71e3-762e-4b1c-a780-5c7792a94027%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
