Re: migrate error in manage.py

Use python3 On Fri, 11 Oct, 2019, 11:01 PM Ralph Barhydt, wrote: > When I try to run "python manage.py migrate" I get an error "invalid > syntax" that points to ") from exc". How can I fix this? > > -- > You received this message because you are subscribed to the Google Groups > "Django users"

migrate error in manage.py

When I try to run "python manage.py migrate" I get an error "invalid syntax" that points to ") from exc". How can I fix this? -- 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, sen

Re: migrate error

Show me your view.py code. On Tue, 10 Sep 2019, 20:03 Chukwuka, wrote: > Might help if you post the migration file 0027.. for testapp > > On Mon, Sep 9, 2019 at 9:29 PM Pradeep Singh > wrote: > >> from django.db import models >> from django import forms >> from django.core import validators >>

Re: migrate error

Might help if you post the migration file 0027.. for testapp On Mon, Sep 9, 2019 at 9:29 PM Pradeep Singh wrote: > from django.db import models > from django import forms > from django.core import validators > from django.core.urlresolvers import reverse > from django.contrib.auth.models import

Re: migrate error

First you can cleanup all migrations files in /migrations/*. And then try to provide *default=" " *for contact_no. Try to migrate all these changes ! On Tue, Sep 10, 2019 at 1:42 PM Pradeep Singh wrote: > okay . yes i did but problem are same > > On Tue, 10 Sep 2019 at 12:49, Rahul Roshan > wro

Re: migrate error

okay . yes i did but problem are same On Tue, 10 Sep 2019 at 12:49, Rahul Roshan wrote: > Can you try contact_date default=" " ! > > On Tue, Sep 10, 2019, 12:22 PM ANi wrote: > >> >> Another piece of advice, please prettify your code or take a screenshot, >> not just paste it directly. >> It

Re: migrate error

Can you try contact_date default=" " ! On Tue, Sep 10, 2019, 12:22 PM ANi wrote: > > Another piece of advice, please prettify your code or take a screenshot, > not just paste it directly. > It is not easy to read to you as well, right? > > > > what had you done in this migration? > Was the ori

Re: migrate error

Another piece of advice, please prettify your code or take a screenshot, not just paste it directly. It is not easy to read to you as well, right? what had you done in this migration? Was the original value in that column a datetime and you want to change it into another data format? Prad

Re: migrate error

from django.db import models from django import forms from django.core import validators from django.core.urlresolvers import reverse from django.contrib.auth.models import User from django.db.models.signals import post_save from django.dispatch import receiver from django.utils import timezone fro

Re: migrate error

Show the code where u have used datetime.datetime. Whenever u are asking something, its better to show code where the error is arised. So it will be easy for others to find the error otherwise no one will answer ur question bro. On Tue, 10 Sep, 2019, 8:14 AM Pradeep Singh, wrote: > I didnot ge

Re: Migrate error

show your migration and model середа, 18 липня 2018 р. 14:44:47 UTC+3 користувач Sophie Obomighie написав: > > Hello, > I attempted to migrate my changes using " Python manage.py migrate " but > I'm getting this error message. > How can I fix this please? > -- You received this message because

Migrate error

Hello, I attempted to migrate my changes using " Python manage.py migrate " but I'm getting this error message. How can I fix this please? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails

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

Re: migrate error

On 23/10/2015 4:23 PM, Christoph Knapp wrote: Ahh OK, the only explanation I have, is that someone already tried to use django on the legacy database and the djando tables were already there. The inspectdb tool put them in the models.py file which caused the error. I did what you said and it work

Re: migrate error

Ahh OK, the only explanation I have, is that someone already tried to use django on the legacy database and the djando tables were already there. The inspectdb tool put them in the models.py file which caused the error. I did what you said and it worked. I just looked at the documentation of the

Re: migrate error

On 22/10/2015 10:40 PM, Christoph Knapp wrote: Hi, I have a legacy database and used "python manage.py inspectdb > models.py" to create a models.py file. After I modified the file all errors went away when I makemigrations. This step works without problems on the only app I have in my project. Wh

migrate error

Hi, I have a legacy database and used "python manage.py inspectdb > models.py" to create a models.py file. After I modified the file all errors went away when I makemigrations. This step works without problems on the only app I have in my project. When I go "python manage.py migrate" I get the