Re: Django 1.9 ./manage.py migrate error

That works for me. You save my life. Thank you! On Friday, June 3, 2016 at 12:26:04 PM UTC-4, Tejesh Papineni wrote: > > its working when already have a db because views.py are using Models from > already existing db. But when creating new db, code in views.py is trying > to access Models that h

Re: Django 1.9 ./manage.py migrate error

its working when already have a db because views.py are using Models from already existing db. But when creating new db, code in views.py is trying to access Models that have not yet been built using ./manage.py migrate. My solution is to comment code in views.py that accesses Models or try exce

Re: Django 1.9 ./manage.py migrate error

Hi, thanks for the reply. So, did you have a db in the project? I cloned the project again and tried to create the db from the model, but using your suggestion doesn't work. I can only get 1.9 working if I already have a db from 1.8, but not creating a new one from scratch. Neither the first or

Re: Django 1.9 ./manage.py migrate error

Ok I had to run these commands to make it work: $manage.py makemigrations $migrate --fake-initial. (for reference: django 1.9.1 / sqlite / OSX / python 3.4) On Sunday, January 17, 2016 at 9:48:22 AM UTC-8, Marisa DeMeglio wrote: > > Did you ever figure this out? I just upgraded from Django 1.8

Re: Django 1.9 ./manage.py migrate error

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

Re: Django 1.9 ./manage.py migrate error

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

Re: Django 1.9 ./manage.py migrate error

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 a

Re: Django 1.9 ./manage.py migrate error

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 i

Re: Django 1.9 ./manage.py migrate error

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 opt

Django 1.9 ./manage.py migrate error

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 t