Re: migrate error in manage.py

2019-10-11 Thread Suraj Thapa FC 
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" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/6843a8cb-be93-4fef-a6f2-f49d6f7a1c98%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPjsHcH3G-JDp1g5ivCrC%3D8PXc78DVZzYfrO4KoLGWZbtyCYNw%40mail.gmail.com.

migrate error in manage.py

2019-10-11 Thread Ralph Barhydt 
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, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6843a8cb-be93-4fef-a6f2-f49d6f7a1c98%40googlegroups.com.

Re: migrate error

2019-09-10 Thread Desh Deepak 
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
>> 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
>> from datetime import datetime
>> # Create your models here.
>> class Contact(models.Model):
>>   name = models.CharField(max_length=200)
>>   email = models.CharField(max_length=100)
>>   phone = models.CharField(max_length=100)
>>   message = models.TextField(blank=True)
>>   contact_date = models.DateTimeField(default=datetime.now, blank=True)
>>
>>   def __str__(self):
>> return self.name
>>
>> class Profile(models.Model):
>> user = models.OneToOneField(User, on_delete=models.CASCADE)
>> bio = models.TextField(max_length=500, blank=True)
>> location = models.CharField(max_length=30, blank=True)
>> #sbirth_date = models.DateField(null=True, blank=True)
>>
>> @receiver(post_save, sender=User)
>> def update_user_profile(sender, instance, created, **kwargs):
>> if created:
>> Profile.objects.create(user=instance)
>> instance.profile.save()
>>
>> class Realtor(models.Model):
>>   name = models.CharField(max_length=200)
>>   photo = models.ImageField(upload_to='media/images/')
>>   description = models.TextField(blank=True)
>>   phone = models.CharField(max_length=20)
>>   email = models.CharField(max_length=50)
>>   is_mvp = models.BooleanField(default=False)
>>   hire_date = models.DateTimeField(default=datetime.now, blank=True)
>>   def __str__(self):
>> return self.name
>>
>> PROPERTY_TYPE = (('Select Property Type','Select Property
>> Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
>> ('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
>> house'),('Residental Land','Residental Land'))
>> TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK', '2
>> BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
>> Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
>> Flat','HIG Flat'))
>> CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'), ('South
>> Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East Delhi','East
>> Delhi'))
>>
>> class Property(models.Model):
>> realtor= models.ForeignKey(Realtor,  on_delete=models.DO_NOTHING)
>> #image=models.ImageField(upload_to='media/images/',blank=True,
>> null=True)
>> house_name=models.CharField(max_length=30)
>> #PROPERTY_TYPE = (('Select Property Type','Select Property
>> Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
>> ('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
>> house'),('Residental Land','Residental Land'))
>> property_type=models.CharField(max_length=20,
>> choices=PROPERTY_TYPE,default='Select Property Type')
>> #TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK',
>> '2 BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
>> Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
>> Flat','HIG Flat'))
>> type=models.CharField(max_length=10,choices=TYPE,default='Select
>> Type')
>> area=models.CharField(max_length=10,blank=False)
>> #CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'),
>> ('South Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East
>> Delhi','East Delhi'))
>> city=models.CharField(max_length=20,choices=CITY,default='Select
>> city')
>> location=models.CharField(max_length=30)
>> price=models.CharField(max_length=20)
>> description=models.TextField(blank=True)
>> publish_date = models.DateTimeField(default=datetime.now, blank=True)
>> publish_date = models.DateTimeField(default=datetime.now, blank=True)
>> image= models.ImageField(upload_to='media/images/',blank=True,
>> null=True )
>> image_1 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> image_2 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> image_3 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> image_4 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> image_5 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> image_6 = models.ImageField(upload_to='media/images/', blank=True ,
>> null=True)
>> #submitted = models.DateField(auto_now_add=True)
>>
>> class Meta:
>> abstract=True
>>
>>
>>
>>
>> class Buy(Property):
>>
>> def __str__(self):
>> return self.house_name
>>
>>
>> class Rent(Property):
>>
>> def __str__(self):
>> return

Re: migrate error

2019-09-10 Thread Chukwuka 
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 User
> from django.db.models.signals import post_save
> from django.dispatch import receiver
> from django.utils import timezone
> from datetime import datetime
> # Create your models here.
> class Contact(models.Model):
>   name = models.CharField(max_length=200)
>   email = models.CharField(max_length=100)
>   phone = models.CharField(max_length=100)
>   message = models.TextField(blank=True)
>   contact_date = models.DateTimeField(default=datetime.now, blank=True)
>
>   def __str__(self):
> return self.name
>
> class Profile(models.Model):
> user = models.OneToOneField(User, on_delete=models.CASCADE)
> bio = models.TextField(max_length=500, blank=True)
> location = models.CharField(max_length=30, blank=True)
> #sbirth_date = models.DateField(null=True, blank=True)
>
> @receiver(post_save, sender=User)
> def update_user_profile(sender, instance, created, **kwargs):
> if created:
> Profile.objects.create(user=instance)
> instance.profile.save()
>
> class Realtor(models.Model):
>   name = models.CharField(max_length=200)
>   photo = models.ImageField(upload_to='media/images/')
>   description = models.TextField(blank=True)
>   phone = models.CharField(max_length=20)
>   email = models.CharField(max_length=50)
>   is_mvp = models.BooleanField(default=False)
>   hire_date = models.DateTimeField(default=datetime.now, blank=True)
>   def __str__(self):
> return self.name
>
> PROPERTY_TYPE = (('Select Property Type','Select Property
> Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
> ('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
> house'),('Residental Land','Residental Land'))
> TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK', '2
> BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
> Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
> Flat','HIG Flat'))
> CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'), ('South
> Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East Delhi','East
> Delhi'))
>
> class Property(models.Model):
> realtor= models.ForeignKey(Realtor,  on_delete=models.DO_NOTHING)
> #image=models.ImageField(upload_to='media/images/',blank=True,
> null=True)
> house_name=models.CharField(max_length=30)
> #PROPERTY_TYPE = (('Select Property Type','Select Property
> Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
> ('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
> house'),('Residental Land','Residental Land'))
> property_type=models.CharField(max_length=20,
> choices=PROPERTY_TYPE,default='Select Property Type')
> #TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK',
> '2 BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
> Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
> Flat','HIG Flat'))
> type=models.CharField(max_length=10,choices=TYPE,default='Select Type')
> area=models.CharField(max_length=10,blank=False)
> #CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'),
> ('South Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East
> Delhi','East Delhi'))
> city=models.CharField(max_length=20,choices=CITY,default='Select city')
> location=models.CharField(max_length=30)
> price=models.CharField(max_length=20)
> description=models.TextField(blank=True)
> publish_date = models.DateTimeField(default=datetime.now, blank=True)
> publish_date = models.DateTimeField(default=datetime.now, blank=True)
> image= models.ImageField(upload_to='media/images/',blank=True,
> null=True )
> image_1 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> image_2 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> image_3 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> image_4 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> image_5 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> image_6 = models.ImageField(upload_to='media/images/', blank=True ,
> null=True)
> #submitted = models.DateField(auto_now_add=True)
>
> class Meta:
> abstract=True
>
>
>
>
> class Buy(Property):
>
> def __str__(self):
> return self.house_name
>
>
> class Rent(Property):
>
> def __str__(self):
> return self.house_name
>
> class PG(Property):
> def __str__(self):
> return self.house_name
>
>
> YOU_ARE=(('Select','Select'),('Owner', 'Owner'), ('Dealer', 'Dealer'),
> ('Agent', 'Agent'))
>

Re: migrate error

2019-09-10 Thread Rahul Roshan 
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 
> 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 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?
>>>
>>>
>>> Pradeep Singh於 2019年9月10日星期二 UTC+8上午10時44分28秒寫道：

  I didnot get why i am getting this error .please help to fix it

>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/8540486f-2bbf-4f39-aa81-82e26cfb352c%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAN%2BO0S4yH%3DoiU5hYfKQK2T-1nSAFF3djqECKADeAXRgf-mPDWw%40mail.gmail.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CANwgZcaVsdbUFagqLC-is802jjvLM91SGiZ270Y2sRNXkSNx5A%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN%2BO0S6UqD99%3D33qJtjj8CNCJo1fRrWJuciYthToUhSUY7g5TQ%40mail.gmail.com.

Re: migrate error

2019-09-10 Thread Pradeep Singh 
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 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?
>>
>>
>> Pradeep Singh於 2019年9月10日星期二 UTC+8上午10時44分28秒寫道：
>>>
>>>  I didnot get why i am getting this error .please help to fix it
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/8540486f-2bbf-4f39-aa81-82e26cfb352c%40googlegroups.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAN%2BO0S4yH%3DoiU5hYfKQK2T-1nSAFF3djqECKADeAXRgf-mPDWw%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANwgZcaVsdbUFagqLC-is802jjvLM91SGiZ270Y2sRNXkSNx5A%40mail.gmail.com.

Re: migrate error

2019-09-10 Thread Rahul Roshan 
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 original value in that column a datetime and you want to change it
> into another data format?
>
>
> Pradeep Singh於 2019年9月10日星期二 UTC+8上午10時44分28秒寫道：
>>
>>  I didnot get why i am getting this error .please help to fix it
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/8540486f-2bbf-4f39-aa81-82e26cfb352c%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN%2BO0S4yH%3DoiU5hYfKQK2T-1nSAFF3djqECKADeAXRgf-mPDWw%40mail.gmail.com.

Re: migrate error

2019-09-10 Thread ANi 

 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?


Pradeep Singh於 2019年9月10日星期二 UTC+8上午10時44分28秒寫道：
>
>  I didnot get why i am getting this error .please help to fix it 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8540486f-2bbf-4f39-aa81-82e26cfb352c%40googlegroups.com.

Re: migrate error

2019-09-09 Thread Pradeep Singh 
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
from datetime import datetime
# Create your models here.
class Contact(models.Model):
  name = models.CharField(max_length=200)
  email = models.CharField(max_length=100)
  phone = models.CharField(max_length=100)
  message = models.TextField(blank=True)
  contact_date = models.DateTimeField(default=datetime.now, blank=True)

  def __str__(self):
return self.name

class Profile(models.Model):
user = models.OneToOneField(User, on_delete=models.CASCADE)
bio = models.TextField(max_length=500, blank=True)
location = models.CharField(max_length=30, blank=True)
#sbirth_date = models.DateField(null=True, blank=True)

@receiver(post_save, sender=User)
def update_user_profile(sender, instance, created, **kwargs):
if created:
Profile.objects.create(user=instance)
instance.profile.save()

class Realtor(models.Model):
  name = models.CharField(max_length=200)
  photo = models.ImageField(upload_to='media/images/')
  description = models.TextField(blank=True)
  phone = models.CharField(max_length=20)
  email = models.CharField(max_length=50)
  is_mvp = models.BooleanField(default=False)
  hire_date = models.DateTimeField(default=datetime.now, blank=True)
  def __str__(self):
return self.name

PROPERTY_TYPE = (('Select Property Type','Select Property
Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
house'),('Residental Land','Residental Land'))
TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK', '2
BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
Flat','HIG Flat'))
CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'), ('South
Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East Delhi','East
Delhi'))

class Property(models.Model):
realtor= models.ForeignKey(Realtor,  on_delete=models.DO_NOTHING)
#image=models.ImageField(upload_to='media/images/',blank=True,
null=True)
house_name=models.CharField(max_length=30)
#PROPERTY_TYPE = (('Select Property Type','Select Property
Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
house'),('Residental Land','Residental Land'))
property_type=models.CharField(max_length=20,
choices=PROPERTY_TYPE,default='Select Property Type')
#TYPE = (('Select Type','Select Type'),('1 BHK', '1 BHK'), ('2 BHK', '2
BHK'), ('3 BHK', '3 BHK'),('4 BHK','4 BHK'),('LAND','Land'),('Janta
Flat','Janta Flat'),('LIG Flat','LIG Flat'),('MIG Flat','MIG Flat'),('HIG
Flat','HIG Flat'))
type=models.CharField(max_length=10,choices=TYPE,default='Select Type')
area=models.CharField(max_length=10,blank=False)
#CITY=(('Select City','Select City'),('West Delhi', 'West Delhi'),
('South Delhi', 'South Delhi'), ('North Delhi', 'North Delhi'),('East
Delhi','East Delhi'))
city=models.CharField(max_length=20,choices=CITY,default='Select city')
location=models.CharField(max_length=30)
price=models.CharField(max_length=20)
description=models.TextField(blank=True)
publish_date = models.DateTimeField(default=datetime.now, blank=True)
publish_date = models.DateTimeField(default=datetime.now, blank=True)
image= models.ImageField(upload_to='media/images/',blank=True,
null=True )
image_1 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
image_2 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
image_3 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
image_4 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
image_5 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
image_6 = models.ImageField(upload_to='media/images/', blank=True ,
null=True)
#submitted = models.DateField(auto_now_add=True)

class Meta:
abstract=True




class Buy(Property):

def __str__(self):
return self.house_name


class Rent(Property):

def __str__(self):
return self.house_name

class PG(Property):
def __str__(self):
return self.house_name


YOU_ARE=(('Select','Select'),('Owner', 'Owner'), ('Dealer', 'Dealer'),
('Agent', 'Agent'))
PROPERTY_FOR=(('Select Property For','Select Property For'), ('Sale',
'Sale'), ('Rent', 'Rent'), ('PG', 'PG'))
PROPERTY_TYPE = (('Select Property Type','Select Property
Type'),('Appartment', 'Appartment'),('DDA Appartment', 'DDA Appartment'),
('Builder Floor', 'Builder Floor'), ('Indepedent house', 'Indepedent
house'),('Residental Land','Residental Land'))

Re: migrate error

2019-09-09 Thread Sipum 
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 get why i am getting this error .please help to fix it
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CANwgZcYfHyD1UGoG_faXv%3DBDnRVcHOBQoQ%3DovUhtV_14VVXmTw%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGHZBzzkphdgsfhkk95vdTd0ZpW0%3Dx0STd4S9x7_LgxgYFk%2BWg%40mail.gmail.com.

Re: Migrate error

2018-07-18 Thread Mikhailo Keda 
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 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/47526442-991a-40ca-871b-468c569cf530%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Migrate error

2018-07-18 Thread 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 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/CAL%3DGykddq86oVC0AdmJmGuyqH%2B5mYBBDLm4FJznBLz0JQ0%2BQjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2017-01-31 Thread Owen Chung 
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 have not yet been built using ./manage.py migrate. My 
> solution is to comment code in views.py that accesses Models or try except 
> with OperationalError , then run migrations (which will work now). 
> Afterwards revert to old views.py code.
>
> On Monday, March 7, 2016 at 4:20:16 AM UTC+5:30, Xuton Ion wrote:
>>
>> 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 second line runs, they both exit with the same 
>> error. Table doesn't exist
>>
>> On Monday, 18 January 2016 08:08:38 UTC+13, Marisa DeMeglio wrote:
>>>
>>> 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 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 
 
  
 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/3cfe5ec1-1643-415c-a299-80bd8135b711%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2016-06-03 Thread Tejesh Papineni 
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 except 
with OperationalError , then run migrations (which will work now). 
Afterwards revert to old views.py code.

On Monday, March 7, 2016 at 4:20:16 AM UTC+5:30, Xuton Ion wrote:
>
> 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 second line runs, they both exit with the same error. 
> Table doesn't exist
>
> On Monday, 18 January 2016 08:08:38 UTC+13, Marisa DeMeglio wrote:
>>
>> 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 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 
>>> 
>>>  
>>> 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/bdf0bcd1-a3c1-4e8e-822d-1962cda5a67b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2016-03-06 Thread Xuton Ion 
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 second line runs, they both exit with the same error. 
Table doesn't exist

On Monday, 18 January 2016 08:08:38 UTC+13, Marisa DeMeglio wrote:
>
> 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 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 
>> 
>>  
>> 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/33f9585a-3432-4769-980f-28f1f2feff59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2016-01-17 Thread Marisa DeMeglio 
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 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 
> 
>  
> 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/31161ef7-6b4b-44de-84bd-a5dc336c087c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2016-01-17 Thread Marisa DeMeglio 
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 
 
  
 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/f6542826-440b-403e-97ab-20aad82b1009%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2015-12-12 Thread Xuton Ion 
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 
>>> 
>>>  
>>> 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/71fbdcc6-9851-4b00-8818-33167f47f927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2015-12-12 Thread Tim Graham 
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 
>> 
>>  
>> 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/19087e81-b933-46de-94c4-d1f2eaac217c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2015-12-12 Thread Xuton Ion 
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 
> 
>  
> 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/c847e7d7-1f2b-45d3-97ef-1a5a6a52b39a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.9 ./manage.py migrate error

2015-12-12 Thread Tim Graham 
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 

 
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.

Django 1.9 ./manage.py migrate error

2015-12-12 Thread Xuton Ion 
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/58bc7f16-83d9-4ea9-82c6-1970b995fa78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: migrate error

2015-10-23 Thread Mike Dewhirst 

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 worked. I just looked at the
documentation of the db and those tables were not in there.


Yes. Sounds reasonable. The other way it can happen is that the legacy 
db was actually created by a Django project and both Admin and Auth were 
installed apps.




Thanks

Christoph


On Thursday, October 22, 2015 at 11:31:11 PM UTC+2, Mike Dewhirst wrote:

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. When I go "python manage.py
 > migrate" I get the following error.
 >
 > Operations to perform:
 > Â  Synchronize unmigrated apps: staticfiles, messages
 > Â  Apply all migrations: admin, contenttypes, sessions, auth,
readDatabase
 > Synchronizing apps without migrations:
 > Â  Creating tables...
 > Â Â Â  Running deferred SQL...
 > Â  Installing custom SQL...
 > Running migrations:
 > Â  Rendering model states... DONE
 > Â  Applying readDatabase.0001_initial...Traceback (most recent
call last):
 > Â  File
 >
"/home/christoph_knapp/Bioinformatik/variantendatenbank_tool/manage.py",

 > line 10, in 
 > Â Â Â  execute_from_command_line(sys.argv)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",

 > line 351, in execute_from_command_line
 > Â Â Â  utility.execute()
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",

 > line 343, in execute
 > Â Â Â  self.fetch_command(subcommand).run_from_argv(self.argv)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",

 > line 394, in run_from_argv
 > Â Â Â  self.execute(*args, **cmd_options)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",

 > line 445, in execute
 > Â Â Â  output = self.handle(*args, **options)
 > Â  File
 >

"/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",

 > line 222, in handle
 > Â Â Â  executor.migrate(targets, plan, fake=fake,
fake_initial=fake_initial)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py",

 > line 110, in migrate
 > Â Â Â  self.apply_migration(states[migration], migration,
fake=fake,
 > fake_initial=fake_initial)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py",

 > line 148, in apply_migration
 > Â Â Â  state = migration.apply(state, schema_editor)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py",

 > line 115, in apply
 > Â Â Â  operation.database_forwards(self.app_label,
schema_editor,
 > old_state, project_state)
 > Â  File
 >

"/usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/models.py",

 > line 59, in database_forwards
 > Â Â Â  schema_editor.create_model(model)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py",

 > line 286, in create_model
 > Â Â Â  self.execute(sql, params or None)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py",

 > line 111, in execute
 > Â Â Â  cursor.execute(sql, params)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
 > line 79, in execute
 > Â Â Â  return super(CursorDebugWrapper, self).execute(sql,
params)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
 > line 64, in execute
 > Â Â Â  return self.cursor.execute(sql, params)
 > Â  File
"/usr/local/lib/python2.7/dist-packages/django/db/utils.py",
 > line 97, in __exit__
 > Â Â Â  six.reraise(dj_exc_type, dj_exc_value, traceback)
 > Â  File
 >
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
 > line 62, in execute
 > Â Â Â  return self.cursor.execute(sql)
 > django.db.utils.ProgrammingError: FEHLER:Â  Relation
„auth_group“
 > existiert bereits
 >
 > The last line contains a little bit of German which translates into
 > "Relation "auth_group" already exists".

Re: migrate error

2015-10-22 Thread Christoph Knapp 
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 db 
and those tables were not in there.

Thanks

Christoph


On Thursday, October 22, 2015 at 11:31:11 PM UTC+2, Mike Dewhirst wrote:
>
> 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. When I go "python manage.py 
> > migrate" I get the following error. 
> > 
> > Operations to perform: 
> > Â  Synchronize unmigrated apps: staticfiles, messages 
> > Â  Apply all migrations: admin, contenttypes, sessions, auth, 
> readDatabase 
> > Synchronizing apps without migrations: 
> > Â  Creating tables... 
> > Â Â Â  Running deferred SQL... 
> > Â  Installing custom SQL... 
> > Running migrations: 
> > Â  Rendering model states... DONE 
> > Â  Applying readDatabase.0001_initial...Traceback (most recent call 
> last): 
> > Â  File 
> > "/home/christoph_knapp/Bioinformatik/variantendatenbank_tool/manage.py", 
> > line 10, in  
> > Â Â Â  execute_from_command_line(sys.argv) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
>
> > line 351, in execute_from_command_line 
> > Â Â Â  utility.execute() 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
>
> > line 343, in execute 
> > Â Â Â  self.fetch_command(subcommand).run_from_argv(self.argv) 
> > Â  File 
> > "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", 
> > line 394, in run_from_argv 
> > Â Â Â  self.execute(*args, **cmd_options) 
> > Â  File 
> > "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", 
> > line 445, in execute 
> > Â Â Â  output = self.handle(*args, **options) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
>  
>
> > line 222, in handle 
> > Â Â Â  executor.migrate(targets, plan, fake=fake, 
> fake_initial=fake_initial) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
> > line 110, in migrate 
> > Â Â Â  self.apply_migration(states[migration], migration, fake=fake, 
> > fake_initial=fake_initial) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
> > line 148, in apply_migration 
> > Â Â Â  state = migration.apply(state, schema_editor) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py", 
> > line 115, in apply 
> > Â Â Â  operation.database_forwards(self.app_label, schema_editor, 
> > old_state, project_state) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/models.py",
>  
>
> > line 59, in database_forwards 
> > Â Â Â  schema_editor.create_model(model) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
> > line 286, in create_model 
> > Â Â Â  self.execute(sql, params or None) 
> > Â  File 
> > 
> "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
> > line 111, in execute 
> > Â Â Â  cursor.execute(sql, params) 
> > Â  File 
> > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", 
> > line 79, in execute 
> > Â Â Â  return super(CursorDebugWrapper, self).execute(sql, params) 
> > Â  File 
> > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", 
> > line 64, in execute 
> > Â Â Â  return self.cursor.execute(sql, params) 
> > Â  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", 
> > line 97, in __exit__ 
> > Â Â Â  six.reraise(dj_exc_type, dj_exc_value, traceback) 
> > Â  File 
> > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", 
> > line 62, in execute 
> > Â Â Â  return self.cursor.execute(sql) 
> > django.db.utils.ProgrammingError: FEHLER:  Relation „auth_group“ 
> > existiert bereits 
> > 
> > The last line contains a little bit of German which translates into 
> > "Relation "auth_group" already exists". The auth_group table was 
> > generated by inspectdb and is none of the tables from the legacy 
> > database. The only change I made at those tables were that I removed the 
> > line "managed=False". When I put this back in I get the same error. The 
> > python code for the auth_group table is below. 
> > 
> > class AuthGroup(models.Model): 
> > Â Â Â  name = models.CharField(unique=True, max_length=80) 
> > 
> > Â Â Â  class Meta: 
> > Â Â Â Â Â Â Â  db_table = 'auth_group' 
>
> auth_group is a Django table which you don't need to install. In your 
> models.py

Re: migrate error

2015-10-22 Thread Mike Dewhirst 

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. When I go "python manage.py
migrate" I get the following error.

Operations to perform:
  Synchronize unmigrated apps: staticfiles, messages
  Apply all migrations: admin, contenttypes, sessions, auth, readDatabase
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying readDatabase.0001_initial...Traceback (most recent call last):
  File
"/home/christoph_knapp/Bioinformatik/variantendatenbank_tool/manage.py",
line 10, in 
    execute_from_command_line(sys.argv)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 351, in execute_from_command_line
    utility.execute()
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 343, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
line 394, in run_from_argv
    self.execute(*args, **cmd_options)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
line 445, in execute
    output = self.handle(*args, **options)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
line 222, in handle
    executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py",
line 110, in migrate
    self.apply_migration(states[migration], migration, fake=fake,
fake_initial=fake_initial)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py",
line 148, in apply_migration
    state = migration.apply(state, schema_editor)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py",
line 115, in apply
    operation.database_forwards(self.app_label, schema_editor,
old_state, project_state)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/models.py",
line 59, in database_forwards
    schema_editor.create_model(model)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py",
line 286, in create_model
    self.execute(sql, params or None)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py",
line 111, in execute
    cursor.execute(sql, params)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py",
line 97, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 62, in execute
    return self.cursor.execute(sql)
django.db.utils.ProgrammingError: FEHLER:  Relation „auth_group“
existiert bereits

The last line contains a little bit of German which translates into
"Relation "auth_group" already exists". The auth_group table was
generated by inspectdb and is none of the tables from the legacy
database. The only change I made at those tables were that I removed the
line "managed=False". When I put this back in I get the same error. The
python code for the auth_group table is below.

class AuthGroup(models.Model):
    name = models.CharField(unique=True, max_length=80)

    class Meta:
        db_table = 'auth_group'


auth_group is a Django table which you don't need to install. In your 
models.py remove all models except your own, drop the database and try 
again. The models/tables created for you by Django and the Admin are ...


auth_group
auth_group_permissions
auth_permission
auth_user
auth_user_groups
auth_user_user_permissions
django_admin_log
django_contenttype
django_migrations
django_session

Cheers

Mike



I just started with django, so let me know whether you need anything else.

Regards

Christoph

--
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

migrate error

2015-10-22 Thread Christoph Knapp 
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 
following error.

Operations to perform:
  Synchronize unmigrated apps: staticfiles, messages
  Apply all migrations: admin, contenttypes, sessions, auth, readDatabase
Synchronizing apps without migrations:
  Creating tables...
Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying readDatabase.0001_initial...Traceback (most recent call last):
  File 
"/home/christoph_knapp/Bioinformatik/variantendatenbank_tool/manage.py", 
line 10, in 
execute_from_command_line(sys.argv)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 351, in execute_from_command_line
utility.execute()
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 343, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", 
line 394, in run_from_argv
self.execute(*args, **cmd_options)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", 
line 445, in execute
output = self.handle(*args, **options)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
 
line 222, in handle
executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 110, in migrate
self.apply_migration(states[migration], migration, fake=fake, 
fake_initial=fake_initial)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 148, in apply_migration
state = migration.apply(state, schema_editor)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py", 
line 115, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, 
project_state)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/models.py",
 
line 59, in database_forwards
schema_editor.create_model(model)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
line 286, in create_model
self.execute(sql, params or None)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
line 111, in execute
cursor.execute(sql, params)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 
79, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 
64, in execute
return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line 
97, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
  File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 
62, in execute
return self.cursor.execute(sql)
django.db.utils.ProgrammingError: FEHLER:  Relation „auth_group“ existiert 
bereits

The last line contains a little bit of German which translates into 
"Relation "auth_group" already exists". The auth_group table was generated 
by inspectdb and is none of the tables from the legacy database. The only 
change I made at those tables were that I removed the line "managed=False". 
When I put this back in I get the same error. The python code for the 
auth_group table is below.

class AuthGroup(models.Model):
name = models.CharField(unique=True, max_length=80)

class Meta:
db_table = 'auth_group'

I just started with django, so let me know whether you need anything else.

Regards

Christoph 

-- 
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/a87703ec-cc25-4404-accf-e5cd800e23c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.