subject:"IntegrityError"

irst in your UploadSerializer fields use fields = "__all__"

Then you can use this in your views:

*def post(self, **request, format=None**):*
*upload_file = request.data.get("upload_file"**)*
*upload_date = **request.data.get("upload_date"**)*


*user = request.userdata = {'upload_file': upload_file,
'upload_date': upload_date, 'user': user}serializer = *
*UploadSerializer*



*(data=data)if serializer.is_valid():serializer.save()
  return Response(serializer.data, status=status.HTTP_201_CREATED)
  return Response(serializer.errors,
status=status.HTTP_400_BAD_REQUEST)*

On Thu, Jul 30, 2020 at 5:59 PM Dinolin yp job 
wrote:

> I don't have forms.py since I'm creating only the endpoints using rest
> framework. I've done it earlier and it has worked but earlier the foreign
> key was to refer the default User model but now I have customized User
> model by extending AbstractBaseUser.
>
> uploads/views.py
>
>
>
>
>
>
> *class UploadView(APIView):def post(self, request,
> format=None):serializer =
> UploadSerializer(data=request.data)if
> serializer.is_valid():serializer.save()return
> Response(serializer.data, status=status.HTTP_201_CREATED)return
> Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)*
>
> uploads/serializers.py
>
>
>
> *class UploadSerializer(serializers.ModelSerializer):class Meta:
> model = Uploadfields = ('upload_file', 'upload_date')*
>
> users/models.py
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *class User(AbstractBaseUser):user_id =
> models.AutoField(primary_key=True)username =
> models.CharField(max_length=50, unique=True)first_name =
> models.CharField(max_length=50)last_name =
> models.CharField(max_length=50)company_name =
> models.CharField(max_length=100)email =
> models.EmailField(max_length=150, unique=True)is_active =
> models.BooleanField(default=True)is_superuser =
> models.BooleanField(default=False)objects = UserManager()
> USERNAME_FIELD = 'username'REQUIRED_FIELDS = ['first_name',
> 'last_name', 'company_name', 'email']def get_full_name(self):
> return self.first_name + self.last_name*
>
>
> On Thursday, July 30, 2020 at 7:59:38 PM UTC+5:30 obast...@gmail.com
> wrote:
>
>> You can create an upload form with an Image field, then when saving the
>> for set the User field to request.user.
>>
>> Do you have an UploadForm already in your forms.py? if yes, show me with
>> the view that handles.
>>
>> On Thu, Jul 30, 2020 at 11:59 AM Dinolin yp job 
>> wrote:
>>
>>>
>>>
>>> It worked but user_id column in uploads_upload table is empty. How to
>>> solve this issue?
>>> On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com
>>> wrote:
>>>
 From the error, it states that you are trying to add an upload object
 to the database without a user. And from your model.py, the User foreign
 key does not have a null=True, and blank=True. So you can't save a null
 value for that user field.

 On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job 
 wrote:

> I'm trying to save image in postgres database. I have upload model
> which has a foreign key reference to the extended custom user model. But 
> it
> shows the following error
>
>
> uploads/model.py
> from django.db import models
> from django.contrib.auth import get_user_model
>
> User = get_user_model()
>
> class Upload(models.Model):
> upload_file = models.ImageField(upload_to='uploads/')
> upload_date = models.DateTimeField(auto_now_add =True)
> user = models.ForeignKey(User, on_delete=models.CASCADE)
>
>
> What am I missing? Thanks in advance
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/e3462364-f867-4187-80bd-abfaa09d86b8n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
>

Re: IntegrityError: null value in column "user_id" violates not-null constraint

first in your UploadSerializer fields use fields = "__all__"

Then you can use this in your views:

*def post(self, **request, format=None**):*
*upload_file = request.data.get("upload_file"**)*
*upload_date = **request.data.get("upload_date"**)*






*user = request.userdata = {'upload_file': upload_file,
'upload_date': upload_date, 'user': user}serializer =
VoteSerializer(data=data)if serializer.is_valid():
serializer.save()return Response(serializer.data,
status=status.HTTP_201_CREATED)return Response(serializer.errors,
status=status.HTTP_400_BAD_REQUEST)*


This should do it for you.

On Thu, Jul 30, 2020 at 5:59 PM Dinolin yp job 
wrote:

> I don't have forms.py since I'm creating only the endpoints using rest
> framework. I've done it earlier and it has worked but earlier the foreign
> key was to refer the default User model but now I have customized User
> model by extending AbstractBaseUser.
>
> uploads/views.py
>
>
>
>
>
>
> *class UploadView(APIView):def post(self, request,
> format=None):serializer =
> UploadSerializer(data=request.data)if
> serializer.is_valid():serializer.save()return
> Response(serializer.data, status=status.HTTP_201_CREATED)return
> Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)*
>
> uploads/serializers.py
>
>
>
> *class UploadSerializer(serializers.ModelSerializer):class Meta:
> model = Uploadfields = ('upload_file', 'upload_date')*
>
> users/models.py
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *class User(AbstractBaseUser):user_id =
> models.AutoField(primary_key=True)username =
> models.CharField(max_length=50, unique=True)first_name =
> models.CharField(max_length=50)last_name =
> models.CharField(max_length=50)company_name =
> models.CharField(max_length=100)email =
> models.EmailField(max_length=150, unique=True)is_active =
> models.BooleanField(default=True)is_superuser =
> models.BooleanField(default=False)objects = UserManager()
> USERNAME_FIELD = 'username'REQUIRED_FIELDS = ['first_name',
> 'last_name', 'company_name', 'email']def get_full_name(self):
> return self.first_name + self.last_name*
>
>
> On Thursday, July 30, 2020 at 7:59:38 PM UTC+5:30 obast...@gmail.com
> wrote:
>
>> You can create an upload form with an Image field, then when saving the
>> for set the User field to request.user.
>>
>> Do you have an UploadForm already in your forms.py? if yes, show me with
>> the view that handles.
>>
>> On Thu, Jul 30, 2020 at 11:59 AM Dinolin yp job 
>> wrote:
>>
>>>
>>>
>>> It worked but user_id column in uploads_upload table is empty. How to
>>> solve this issue?
>>> On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com
>>> wrote:
>>>
 From the error, it states that you are trying to add an upload object
 to the database without a user. And from your model.py, the User foreign
 key does not have a null=True, and blank=True. So you can't save a null
 value for that user field.

 On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job 
 wrote:

> I'm trying to save image in postgres database. I have upload model
> which has a foreign key reference to the extended custom user model. But 
> it
> shows the following error
>
>
> uploads/model.py
> from django.db import models
> from django.contrib.auth import get_user_model
>
> User = get_user_model()
>
> class Upload(models.Model):
> upload_file = models.ImageField(upload_to='uploads/')
> upload_date = models.DateTimeField(auto_now_add =True)
> user = models.ForeignKey(User, on_delete=models.CASCADE)
>
>
> What am I missing? Thanks in advance
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/e3462364-f867-4187-80bd-abfaa09d86b8n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google

Re: IntegrityError: null value in column "user_id" violates not-null constraint

I don't have forms.py since I'm creating only the endpoints using rest 
framework. I've done it earlier and it has worked but earlier the foreign 
key was to refer the default User model but now I have customized User 
model by extending AbstractBaseUser. 

uploads/views.py






*class UploadView(APIView):def post(self, request, format=None):
serializer = UploadSerializer(data=request.data)if 
serializer.is_valid():serializer.save()return 
Response(serializer.data, status=status.HTTP_201_CREATED)return 
Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)*

uploads/serializers.py



*class UploadSerializer(serializers.ModelSerializer):class Meta:
model = Uploadfields = ('upload_file', 'upload_date')*

users/models.py
















*class User(AbstractBaseUser):user_id = 
models.AutoField(primary_key=True)username = 
models.CharField(max_length=50, unique=True)first_name = 
models.CharField(max_length=50)last_name = 
models.CharField(max_length=50)company_name = 
models.CharField(max_length=100)email = 
models.EmailField(max_length=150, unique=True)is_active = 
models.BooleanField(default=True)is_superuser = 
models.BooleanField(default=False)objects = UserManager()
USERNAME_FIELD = 'username'REQUIRED_FIELDS = ['first_name', 
'last_name', 'company_name', 'email']def get_full_name(self):
return self.first_name + self.last_name*


On Thursday, July 30, 2020 at 7:59:38 PM UTC+5:30 obast...@gmail.com wrote:

> You can create an upload form with an Image field, then when saving the 
> for set the User field to request.user.
>
> Do you have an UploadForm already in your forms.py? if yes, show me with 
> the view that handles.
>
> On Thu, Jul 30, 2020 at 11:59 AM Dinolin yp job  
> wrote:
>
>>
>>
>> It worked but user_id column in uploads_upload table is empty. How to 
>> solve this issue?
>> On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com 
>> wrote:
>>
>>> From the error, it states that you are trying to add an upload object to 
>>> the database without a user. And from your model.py, the User foreign key 
>>> does not have a null=True, and blank=True. So you can't save a null value 
>>> for that user field. 
>>>
>>> On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job  
>>> wrote:
>>>
 I'm trying to save image in postgres database. I have upload model 
 which has a foreign key reference to the extended custom user model. But 
 it 
 shows the following error


 uploads/model.py
 from django.db import models
 from django.contrib.auth import get_user_model

 User = get_user_model()

 class Upload(models.Model):
 upload_file = models.ImageField(upload_to='uploads/')
 upload_date = models.DateTimeField(auto_now_add =True)
 user = models.ForeignKey(User, on_delete=models.CASCADE)


 What am I missing? Thanks in advance

 -- 
 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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/e3462364-f867-4187-80bd-abfaa09d86b8n%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/0ce310b5-7bf5-4200-8ddd-e679c160669dn%40googlegroups.com.

Re: IntegrityError: null value in column "user_id" violates not-null constraint

You can create an upload form with an Image field, then when saving the for
set the User field to request.user.

Do you have an UploadForm already in your forms.py? if yes, show me with
the view that handles.

On Thu, Jul 30, 2020 at 11:59 AM Dinolin yp job 
wrote:

>
>
> It worked but user_id column in uploads_upload table is empty. How to
> solve this issue?
> On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com
> wrote:
>
>> From the error, it states that you are trying to add an upload object to
>> the database without a user. And from your model.py, the User foreign key
>> does not have a null=True, and blank=True. So you can't save a null value
>> for that user field.
>>
>> On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job 
>> wrote:
>>
>>> I'm trying to save image in postgres database. I have upload model which
>>> has a foreign key reference to the extended custom user model. But it shows
>>> the following error
>>>
>>>
>>> uploads/model.py
>>> from django.db import models
>>> from django.contrib.auth import get_user_model
>>>
>>> User = get_user_model()
>>>
>>> class Upload(models.Model):
>>> upload_file = models.ImageField(upload_to='uploads/')
>>> upload_date = models.DateTimeField(auto_now_add =True)
>>> user = models.ForeignKey(User, on_delete=models.CASCADE)
>>>
>>>
>>> What am I missing? Thanks in advance
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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/e3462364-f867-4187-80bd-abfaa09d86b8n%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/CAAJsLnrbpKP1%3DN76ZccFmDv%3DswShpBrYHgeAZxnDoYP-MyZ3XQ%40mail.gmail.com.

Re: IntegrityError: null value in column "user_id" violates not-null constraint



It worked but user_id column in uploads_upload table is empty. How to solve 
this issue?
On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com wrote:

> From the error, it states that you are trying to add an upload object to 
> the database without a user. And from your model.py, the User foreign key 
> does not have a null=True, and blank=True. So you can't save a null value 
> for that user field. 
>
> On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job  
> wrote:
>
>> I'm trying to save image in postgres database. I have upload model which 
>> has a foreign key reference to the extended custom user model. But it shows 
>> the following error
>>
>>
>> uploads/model.py
>> from django.db import models
>> from django.contrib.auth import get_user_model
>>
>> User = get_user_model()
>>
>> class Upload(models.Model):
>> upload_file = models.ImageField(upload_to='uploads/')
>> upload_date = models.DateTimeField(auto_now_add =True)
>> user = models.ForeignKey(User, on_delete=models.CASCADE)
>>
>>
>> What am I missing? Thanks in advance
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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/e3462364-f867-4187-80bd-abfaa09d86b8n%40googlegroups.com.

Re: IntegrityError: null value in column "user_id" violates not-null constraint



It worked but the user_id in uploads_upload is empty. How can I can make 
that work?
On Thursday, July 30, 2020 at 3:31:21 PM UTC+5:30 obast...@gmail.com wrote:

> From the error, it states that you are trying to add an upload object to 
> the database without a user. And from your model.py, the User foreign key 
> does not have a null=True, and blank=True. So you can't save a null value 
> for that user field. 
>
> On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job  
> wrote:
>
>> I'm trying to save image in postgres database. I have upload model which 
>> has a foreign key reference to the extended custom user model. But it shows 
>> the following error
>>
>>
>> uploads/model.py
>> from django.db import models
>> from django.contrib.auth import get_user_model
>>
>> User = get_user_model()
>>
>> class Upload(models.Model):
>> upload_file = models.ImageField(upload_to='uploads/')
>> upload_date = models.DateTimeField(auto_now_add =True)
>> user = models.ForeignKey(User, on_delete=models.CASCADE)
>>
>>
>> What am I missing? Thanks in advance
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bddd1f92-895c-4e23-8f08-976c0f178f17o%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/57100db3-81b7-49ca-86e6-096c121c94c8n%40googlegroups.com.

Re: IntegrityError: null value in column "user_id" violates not-null constraint

>From the error, it states that you are trying to add an upload object to
the database without a user. And from your model.py, the User foreign key
does not have a null=True, and blank=True. So you can't save a null value
for that user field.

On Thu, Jul 30, 2020 at 10:52 AM Dinolin yp job 
wrote:

> I'm trying to save image in postgres database. I have upload model which
> has a foreign key reference to the extended custom user model. But it shows
> the following error
>
>
> uploads/model.py
> from django.db import models
> from django.contrib.auth import get_user_model
>
> User = get_user_model()
>
> class Upload(models.Model):
> upload_file = models.ImageField(upload_to='uploads/')
> upload_date = models.DateTimeField(auto_now_add =True)
> user = models.ForeignKey(User, on_delete=models.CASCADE)
>
>
> What am I missing? Thanks in advance
>
> --
> 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/bddd1f92-895c-4e23-8f08-976c0f178f17o%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/CAAJsLno%2BZ14h9Z%3DHxkFWoqkA7k%3DtgLtuSmST-epu_wKPSaFpFw%40mail.gmail.com.

IntegrityError: null value in column "user_id" violates not-null constraint

I'm trying to save image in postgres database. I have upload model which 
has a foreign key reference to the extended custom user model. But it shows 
the following error


uploads/model.py
from django.db import models
from django.contrib.auth import get_user_model

User = get_user_model()

class Upload(models.Model):
upload_file = models.ImageField(upload_to='uploads/')
upload_date = models.DateTimeField(auto_now_add =True)
user = models.ForeignKey(User, on_delete=models.CASCADE)


What am I missing? Thanks in advance

-- 
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/bddd1f92-895c-4e23-8f08-976c0f178f17o%40googlegroups.com.

Re: IntegrityError: NOT NULL constraint failed

2020-05-27 Thread sunday honesty

Thanks Samuel it worked

On Thu, May 28, 2020, 12:23 AM Samuel Nogueira  wrote:

> In your Comment model you have a author field wich is a ForeignKey. The
> error is pointing exactly to that field, since it is a not null field. To
> overcome this you must pick the ID of the logged user and set the author
> field with the user ID. You can do that in your views.py the same way as
> you did in new_comment.post = post, only changing .post for .author and
> matching it with request.user. the line will look like this
> new_comment.author = request.user. remember to put it before
> new_comment.save()
>
>
>
> *De: *sunday honesty 
> *Enviado:*quarta-feira, 27 de maio de 2020 19:36
> *Para: *Django users 
> *Assunto: *IntegrityError: NOT NULL constraint failed
>
>
>
> I try to let user add comments to blog post am making... When I run
> makemigrations and migrate, everything seemed fine . The form displayed
> well but shows the following error when I fill the form and click on the
> submit button. Django.db.utils.IntegrityError: NOT NULL constraint failed:
> blog_comment.author_id
>
>
>
> Am new to Django and following a tutorial. The tutorial doesn't have users
> except the super user. I learnt about users and so I let user register to
> use the blog. The tutorial provided a name field in the form so commenter
> can enter their name. Here, I want to use the current user for this
> field(see my models.py below to see how I have done this). Any help to
> solve this will be appreciated.
>
>
>
> PS: I have seen similar questions like this and deleted my migrations file
> and re-ran migrations but it didn't still work.
>
>
>
> #models.py
>
> class Comment(models.Model):
>
> post = models.ForeignKey(Post, on_delete=models.CASCADE,
> related_name='comments')
>
> author = models.ForeignKey(get_user_model(), on_delete=models.CASCADE,)
>
> comment = models.TextField()
>
> created = models.DateTimeField(auto_now_add=True)
>
> updated = models.DateTimeField(auto_now=True)
>
> active = models.BooleanField(default=True)
>
>
>
> class Meta:
>
> ordering = ('created',)
>
>
>
> def __str__(self):
>
> return f'Comment by {self.author} on {self.post}'
>
>
>
> #forms.py
>
> class CommentForm(forms.ModelForm):
>
>
>
> class Meta:
>
> model = Comment
>
> fields = ('comment',)
>
>
>
> #views.py
>
> login_required
>
> def post_detail(request, post, pk):
>
> post = get_object_or_404(Post, id=pk, slug=post, status='published')
>
> comments = post.comments.filter(active=True)
>
> new_comment = None
>
>
>
> if request.method == 'POST':
>
> comment_form = CommentForm(data=request.POST)
>
> if comment_form.is_valid():
>
> new_comment = comment_form.save(commit=False)
>
> new_comment.post = post
>
> new_comment.save()
>
> else:
>
> comment_form = CommentForm()
>
> return render(request,
>
> 'post_detail.html',
>
> {'post': post,
>
> 'comments': comments,
>
> 'new_comment': new_comment,
>
> 'comment_form': comment_form})
>
>
>
> --
>
> 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/87349ba6-bb75-477c-a84b-9e15be428a5b%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/5ecef62c.1c69fb81.ab057.4da7%40mx.google.com
> <https://groups.google.com/d/msgid/django-users/5ecef62c.1c69fb81.ab057.4da7%40mx.google.com?utm_medium=email_source=footer>
> .
>

-- 
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/CALcuGNtreJ4koB6v22TtGKsPSD9-w4%3DzFR_v63u5c%3Dk6rNJUXA%40mail.gmail.com.

RES: IntegrityError: NOT NULL constraint failed

2020-05-27 Thread Samuel Nogueira

In your Comment model you have a author field wich is a ForeignKey. The error is pointing exactly to that field, since it is a not null field. To overcome this you must pick the ID of the logged user and set the author field with the user ID. You can do that in your views.py the same way as you did in new_comment.post = post, only changing .post for .author and matching it with request.user. the line will look like this new_comment.author = request.user. remember to put it before new_comment.save()  De: sunday honestyEnviado:quarta-feira, 27 de maio de 2020 19:36Para: Django usersAssunto: IntegrityError: NOT NULL constraint failed I try to let user add comments to blog post am making... When I run makemigrations and migrate, everything seemed fine . The form displayed well but shows the following error when I fill the form and click on the submit button. Django.db.utils.IntegrityError: NOT NULL constraint failed: blog_comment.author_id Am new to Django and following a tutorial. The tutorial doesn't have users except the super user. I learnt about users and so I let user register to use the blog. The tutorial provided a name field in the form so commenter can enter their name. Here, I want to use the current user for this field(see my models.py below to see how I have done this). Any help to solve this will be appreciated. PS: I have seen similar questions like this and deleted my migrations file and re-ran migrations but it didn't still work. #models.pyclass Comment(models.Model):    post = models.ForeignKey(Post, _on_delete_=models.CASCADE, related_name='comments')    author = models.ForeignKey(get_user_model(), _on_delete_=models.CASCADE,)    comment = models.TextField()   created = models.DateTimeField(auto_now_add=True)  updated = models.DateTimeField(auto_now=True)    active = models.BooleanField(default=True) class Meta:    ordering = ('created',) def __str__(self):    return f'Comment by {self.author} on {self.post}' #forms.pyclass CommentForm(forms.ModelForm): class Meta:    model = Comment    fields = ('comment',) #views.pylogin_requireddef post_detail(request, post, pk):    post = get_object_or_404(Post, id=pk, slug=post, status='published')    comments = post.comments.filter(active=True)    new_comment = None if request.method == 'POST':    comment_form = CommentForm(data="">    if comment_form.is_valid():    new_comment = comment_form.save(commit=False)    new_comment.post = post    new_comment.save()    else:    comment_form = CommentForm()    return render(request,    'post_detail.html',    {'post': post,    'comments': comments,    'new_comment': new_comment,    'comment_form': comment_form}) -- 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/87349ba6-bb75-477c-a84b-9e15be428a5b%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/5ecef62c.1c69fb81.ab057.4da7%40mx.google.com.

IntegrityError: NOT NULL constraint failed

2020-05-27 Thread sunday honesty

I try to let user add comments to blog post am making... When I run 
makemigrations and migrate, everything seemed fine . The form displayed well 
but shows the following error when I fill the form and click on the submit 
button. Django.db.utils.IntegrityError: NOT NULL constraint failed: 
blog_comment.author_id

Am new to Django and following a tutorial. The tutorial doesn't have users 
except the super user. I learnt about users and so I let user register to use 
the blog. The tutorial provided a name field in the form so commenter can enter 
their name. Here, I want to use the current user for this field(see my 
models.py below to see how I have done this). Any help to solve this will be 
appreciated.

PS: I have seen similar questions like this and deleted my migrations file and 
re-ran migrations but it didn't still work.

#models.py
class Comment(models.Model):
post = models.ForeignKey(Post, on_delete=models.CASCADE, 
related_name='comments')
author = models.ForeignKey(get_user_model(), on_delete=models.CASCADE,)
comment = models.TextField()   
created = models.DateTimeField(auto_now_add=True)  
updated = models.DateTimeField(auto_now=True)
active = models.BooleanField(default=True)

class Meta:
ordering = ('created',)

def __str__(self):
return f'Comment by {self.author} on {self.post}'

#forms.py
class CommentForm(forms.ModelForm):

class Meta:
model = Comment
fields = ('comment',)

#views.py
login_required
def post_detail(request, post, pk):
post = get_object_or_404(Post, id=pk, slug=post, status='published')
comments = post.comments.filter(active=True)
new_comment = None

if request.method == 'POST':
comment_form = CommentForm(data=request.POST)
if comment_form.is_valid():
new_comment = comment_form.save(commit=False)
new_comment.post = post
new_comment.save()
else:
comment_form = CommentForm()
return render(request,
'post_detail.html',
{'post': post,
'comments': comments,
'new_comment': new_comment,
'comment_form': comment_form})

-- 
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/87349ba6-bb75-477c-a84b-9e15be428a5b%40googlegroups.com.

Re: UniqueConstraint raises uncaught IntegrityError in Admin

2019-07-17 Thread Michael Barr

That's what I had to revert to doing, yes. I added logic to the 
validate_unique() method on the model itself and then updated the query 
logic manually.

On Wednesday, July 17, 2019 at 2:15:52 AM UTC-4, Derek wrote:
>
> Would it be correct to say that adding validation at model clean level 
> would make more sense when using this feature with the admin?
>
> On Tuesday, 9 April 2019 15:13:19 UTC+2, Simon Charette wrote:
>>
>> No form validation is implemented for UniqueConstraint(condition) yet as 
>> that would require
>> a non-trivial refactor of how it's performed. It was discussed during the 
>> feature development[0].
>>
>> I'd suggest you override you form or your model's clean() method to 
>> perform the validation
>> yourself until built-in support is added.
>>
>> Submitting a new Trac ticket so we don't loose track of the issue would 
>> also be appreciated.
>>
>> Cheers,
>> Simon
>>
>> [0] https://github.com/django/django/pull/10796#discussion_r244216763
>>
>> Le mardi 9 avril 2019 07:29:53 UTC-4, Ryan Jarvis a écrit :
>>>
>>> Hey there,
>>>
>>> I'm trying out the new UniqueConstraint functionality in Django 2.2 and 
>>> seem to be misunderstanding something.  When adding a Constraint to the 
>>> model I am getting an uncaught IntegrityError in the admin.  
>>> I've got the following sample code:
>>>
>>> *models.py*
>>>
>>> class Seminar(models.Model):
>>> seminar_id = models.CharField(max_length=255, unique=True)
>>> members = models.ManyToManyField(User, through='SeminarRole', 
>>> related_name="studies")
>>>
>>> class SeminarRole(models.Model):
>>> LEAD = 1  # Only 1 Lead permitted per seminar
>>> SUPPORT = 2
>>> ROLE_CHOICES = (
>>> (LEAD, 'Lead'),
>>> (SUPPORT, 'Support'),
>>> )
>>>
>>> user = models.ForeignKey(User, related_name='seminar_roles', 
>>> on_delete=models.CASCADE)
>>> seminar = models.ForeignKey('seminar', related_name='roles', 
>>> on_delete=models.CASCADE)
>>>
>>> role = models.IntegerField(choices=ROLE_CHOICES)
>>>
>>> class Meta:
>>> constraints = [
>>> models.UniqueConstraint(fields=['seminar'], 
>>> condition=Q(role=1), name="only_one_lead"),
>>> ]
>>>
>>>
>>>
>>> For the code above in the Django Admin I can successfully add a 
>>> SeminarRole with User1 as the Lead for SeminarA, User2 as the Lead for 
>>> SeminarB, and User1 as Support for SeminarB but if I try and add User2 as 
>>> another Lead to SeminarA it gives me an Exception.  Should I be seeing the 
>>> Django Admin catch this before hand?
>>>
>>> IntegrityError at /admin/study_management/seminarrole/add/
>>> duplicate key value violates unique constraint "only_one_lead"
>>> DETAIL:  Key (seminar_id)=(1) already exists.
>>>
>>>
>>> I'm on Django 2.2, Python 3.7 and Postgres 11.2
>>>
>>>

-- 
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/54a5cda6-000d-4f2d-8260-1e0765c33d84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UniqueConstraint raises uncaught IntegrityError in Admin

2019-07-17 Thread Derek

Would it be correct to say that adding validation at model clean level 
would make more sense when using this feature with the admin?

On Tuesday, 9 April 2019 15:13:19 UTC+2, Simon Charette wrote:
>
> No form validation is implemented for UniqueConstraint(condition) yet as 
> that would require
> a non-trivial refactor of how it's performed. It was discussed during the 
> feature development[0].
>
> I'd suggest you override you form or your model's clean() method to 
> perform the validation
> yourself until built-in support is added.
>
> Submitting a new Trac ticket so we don't loose track of the issue would 
> also be appreciated.
>
> Cheers,
> Simon
>
> [0] https://github.com/django/django/pull/10796#discussion_r244216763
>
> Le mardi 9 avril 2019 07:29:53 UTC-4, Ryan Jarvis a écrit :
>>
>> Hey there,
>>
>> I'm trying out the new UniqueConstraint functionality in Django 2.2 and 
>> seem to be misunderstanding something.  When adding a Constraint to the 
>> model I am getting an uncaught IntegrityError in the admin.  
>> I've got the following sample code:
>>
>> *models.py*
>>
>> class Seminar(models.Model):
>> seminar_id = models.CharField(max_length=255, unique=True)
>> members = models.ManyToManyField(User, through='SeminarRole', 
>> related_name="studies")
>>
>> class SeminarRole(models.Model):
>> LEAD = 1  # Only 1 Lead permitted per seminar
>> SUPPORT = 2
>> ROLE_CHOICES = (
>> (LEAD, 'Lead'),
>> (SUPPORT, 'Support'),
>> )
>>
>> user = models.ForeignKey(User, related_name='seminar_roles', 
>> on_delete=models.CASCADE)
>> seminar = models.ForeignKey('seminar', related_name='roles', 
>> on_delete=models.CASCADE)
>>
>> role = models.IntegerField(choices=ROLE_CHOICES)
>>
>> class Meta:
>> constraints = [
>> models.UniqueConstraint(fields=['seminar'], 
>> condition=Q(role=1), name="only_one_lead"),
>> ]
>>
>>
>>
>> For the code above in the Django Admin I can successfully add a 
>> SeminarRole with User1 as the Lead for SeminarA, User2 as the Lead for 
>> SeminarB, and User1 as Support for SeminarB but if I try and add User2 as 
>> another Lead to SeminarA it gives me an Exception.  Should I be seeing the 
>> Django Admin catch this before hand?
>>
>> IntegrityError at /admin/study_management/seminarrole/add/
>> duplicate key value violates unique constraint "only_one_lead"
>> DETAIL:  Key (seminar_id)=(1) already exists.
>>
>>
>> I'm on Django 2.2, Python 3.7 and Postgres 11.2
>>
>>

-- 
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/acce73e7-b15c-4efc-9e30-bfb40510c8a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UniqueConstraint raises uncaught IntegrityError in Admin

2019-07-15 Thread Michael Barr

Yeah, this one just bit me in the Django Admin as well. According to the 
docs <https://docs.djangoproject.com/en/2.2/ref/models/constraints/>,

Validation of Constraints
>
> In general constraints are *not* checked during full_clean(), and do not 
> raise ValidationErrors. Rather you’ll get a database integrity error on 
> save(). UniqueConstraints are different in this regard, in that they 
> leverage the existing validate_unique() logic, and thus enable two-stage 
> validation. In addition to IntegrityError on save(), ValidationError is 
> also raised during model validation when the UniqueConstraint is violated.
>

However, it makes no mention of UniqueConstraint instances with conditions 
being ignored. It took me diving into the Django source code to find out 
what was happening. Thankfully, I stumbled upon this here to confirm my 
sanity. :)

On Tuesday, April 9, 2019 at 9:13:19 AM UTC-4, Simon Charette wrote:
>
> No form validation is implemented for UniqueConstraint(condition) yet as 
> that would require
> a non-trivial refactor of how it's performed. It was discussed during the 
> feature development[0].
>
> I'd suggest you override you form or your model's clean() method to 
> perform the validation
> yourself until built-in support is added.
>
> Submitting a new Trac ticket so we don't loose track of the issue would 
> also be appreciated.
>
> Cheers,
> Simon
>
> [0] https://github.com/django/django/pull/10796#discussion_r244216763
>
> Le mardi 9 avril 2019 07:29:53 UTC-4, Ryan Jarvis a écrit :
>>
>> Hey there,
>>
>> I'm trying out the new UniqueConstraint functionality in Django 2.2 and 
>> seem to be misunderstanding something.  When adding a Constraint to the 
>> model I am getting an uncaught IntegrityError in the admin.  
>> I've got the following sample code:
>>
>> *models.py*
>>
>> class Seminar(models.Model):
>> seminar_id = models.CharField(max_length=255, unique=True)
>> members = models.ManyToManyField(User, through='SeminarRole', 
>> related_name="studies")
>>
>> class SeminarRole(models.Model):
>> LEAD = 1  # Only 1 Lead permitted per seminar
>> SUPPORT = 2
>> ROLE_CHOICES = (
>> (LEAD, 'Lead'),
>> (SUPPORT, 'Support'),
>> )
>>
>> user = models.ForeignKey(User, related_name='seminar_roles', 
>> on_delete=models.CASCADE)
>> seminar = models.ForeignKey('seminar', related_name='roles', 
>> on_delete=models.CASCADE)
>>
>> role = models.IntegerField(choices=ROLE_CHOICES)
>>
>> class Meta:
>> constraints = [
>> models.UniqueConstraint(fields=['seminar'], 
>> condition=Q(role=1), name="only_one_lead"),
>> ]
>>
>>
>>
>> For the code above in the Django Admin I can successfully add a 
>> SeminarRole with User1 as the Lead for SeminarA, User2 as the Lead for 
>> SeminarB, and User1 as Support for SeminarB but if I try and add User2 as 
>> another Lead to SeminarA it gives me an Exception.  Should I be seeing the 
>> Django Admin catch this before hand?
>>
>> IntegrityError at /admin/study_management/seminarrole/add/
>> duplicate key value violates unique constraint "only_one_lead"
>> DETAIL:  Key (seminar_id)=(1) already exists.
>>
>>
>> I'm on Django 2.2, Python 3.7 and Postgres 11.2
>>
>>

-- 
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/e0a79eab-e9d6-46fb-86c3-8f5d97fb3f7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UniqueConstraint raises uncaught IntegrityError in Admin

2019-04-09 Thread Simon Charette

No form validation is implemented for UniqueConstraint(condition) yet as 
that would require
a non-trivial refactor of how it's performed. It was discussed during the 
feature development[0].

I'd suggest you override you form or your model's clean() method to perform 
the validation
yourself until built-in support is added.

Submitting a new Trac ticket so we don't loose track of the issue would 
also be appreciated.

Cheers,
Simon

[0] https://github.com/django/django/pull/10796#discussion_r244216763

Le mardi 9 avril 2019 07:29:53 UTC-4, Ryan Jarvis a écrit :
>
> Hey there,
>
> I'm trying out the new UniqueConstraint functionality in Django 2.2 and 
> seem to be misunderstanding something.  When adding a Constraint to the 
> model I am getting an uncaught IntegrityError in the admin.  
> I've got the following sample code:
>
> *models.py*
>
> class Seminar(models.Model):
> seminar_id = models.CharField(max_length=255, unique=True)
> members = models.ManyToManyField(User, through='SeminarRole', 
> related_name="studies")
>
> class SeminarRole(models.Model):
> LEAD = 1  # Only 1 Lead permitted per seminar
> SUPPORT = 2
> ROLE_CHOICES = (
> (LEAD, 'Lead'),
> (SUPPORT, 'Support'),
> )
>
> user = models.ForeignKey(User, related_name='seminar_roles', 
> on_delete=models.CASCADE)
> seminar = models.ForeignKey('seminar', related_name='roles', 
> on_delete=models.CASCADE)
>
> role = models.IntegerField(choices=ROLE_CHOICES)
>
> class Meta:
> constraints = [
> models.UniqueConstraint(fields=['seminar'], 
> condition=Q(role=1), name="only_one_lead"),
> ]
>
>
>
> For the code above in the Django Admin I can successfully add a 
> SeminarRole with User1 as the Lead for SeminarA, User2 as the Lead for 
> SeminarB, and User1 as Support for SeminarB but if I try and add User2 as 
> another Lead to SeminarA it gives me an Exception.  Should I be seeing the 
> Django Admin catch this before hand?
>
> IntegrityError at /admin/study_management/seminarrole/add/
> duplicate key value violates unique constraint "only_one_lead"
> DETAIL:  Key (seminar_id)=(1) already exists.
>
>
> I'm on Django 2.2, Python 3.7 and Postgres 11.2
>
>

-- 
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/12fba4e5-7f07-4491-afb6-b969e73252da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UniqueConstraint raises uncaught IntegrityError in Admin

2019-04-09 Thread Robin Riis

The Integrity error means that there is a row in the database with role = 1
So another row with role=1 would break the unique constraint and is not
allowed.

So either remove the unique constraint or make sure it will be unique.

Den tis 9 apr. 2019 13:29Ryan Jarvis  skrev:

> Hey there,
>
> I'm trying out the new UniqueConstraint functionality in Django 2.2 and
> seem to be misunderstanding something.  When adding a Constraint to the
> model I am getting an uncaught IntegrityError in the admin.
> I've got the following sample code:
>
> *models.py*
>
> class Seminar(models.Model):
> seminar_id = models.CharField(max_length=255, unique=True)
> members = models.ManyToManyField(User, through='SeminarRole',
> related_name="studies")
>
> class SeminarRole(models.Model):
> LEAD = 1  # Only 1 Lead permitted per seminar
> SUPPORT = 2
> ROLE_CHOICES = (
> (LEAD, 'Lead'),
> (SUPPORT, 'Support'),
> )
>
> user = models.ForeignKey(User, related_name='seminar_roles',
> on_delete=models.CASCADE)
> seminar = models.ForeignKey('seminar', related_name='roles',
> on_delete=models.CASCADE)
>
> role = models.IntegerField(choices=ROLE_CHOICES)
>
> class Meta:
> constraints = [
> models.UniqueConstraint(fields=['seminar'],
> condition=Q(role=1), name="only_one_lead"),
> ]
>
>
>
> For the code above in the Django Admin I can successfully add a
> SeminarRole with User1 as the Lead for SeminarA, User2 as the Lead for
> SeminarB, and User1 as Support for SeminarB but if I try and add User2 as
> another Lead to SeminarA it gives me an Exception.  Should I be seeing the
> Django Admin catch this before hand?
>
> IntegrityError at /admin/study_management/seminarrole/add/
> duplicate key value violates unique constraint "only_one_lead"
> DETAIL:  Key (seminar_id)=(1) already exists.
>
>
> I'm on Django 2.2, Python 3.7 and Postgres 11.2
>
> --
> 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/fb2ab520-178d-4a0c-acf7-8cb0498936e4%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/fb2ab520-178d-4a0c-acf7-8cb0498936e4%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPLZMbPxNN%3DCa6GqjcR_kXDO_a2VyzKxgVNfTgzAdtnfhhYqgA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

UniqueConstraint raises uncaught IntegrityError in Admin

2019-04-09 Thread Ryan Jarvis

Hey there,

I'm trying out the new UniqueConstraint functionality in Django 2.2 and 
seem to be misunderstanding something.  When adding a Constraint to the 
model I am getting an uncaught IntegrityError in the admin.  
I've got the following sample code:

*models.py*

class Seminar(models.Model):
seminar_id = models.CharField(max_length=255, unique=True)
members = models.ManyToManyField(User, through='SeminarRole', 
related_name="studies")

class SeminarRole(models.Model):
LEAD = 1  # Only 1 Lead permitted per seminar
SUPPORT = 2
ROLE_CHOICES = (
(LEAD, 'Lead'),
(SUPPORT, 'Support'),
)

user = models.ForeignKey(User, related_name='seminar_roles', 
on_delete=models.CASCADE)
seminar = models.ForeignKey('seminar', related_name='roles', 
on_delete=models.CASCADE)

role = models.IntegerField(choices=ROLE_CHOICES)

class Meta:
constraints = [
models.UniqueConstraint(fields=['seminar'], 
condition=Q(role=1), name="only_one_lead"),
]



For the code above in the Django Admin I can successfully add a SeminarRole 
with User1 as the Lead for SeminarA, User2 as the Lead for SeminarB, and 
User1 as Support for SeminarB but if I try and add User2 as another Lead to 
SeminarA it gives me an Exception.  Should I be seeing the Django Admin 
catch this before hand?

IntegrityError at /admin/study_management/seminarrole/add/
duplicate key value violates unique constraint "only_one_lead"
DETAIL:  Key (seminar_id)=(1) already exists.


I'm on Django 2.2, Python 3.7 and Postgres 11.2

-- 
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/fb2ab520-178d-4a0c-acf7-8cb0498936e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Need your help to fix IntegrityError in my Django code.

2018-07-02 Thread prateek gupta

Hi All,

I have created a simple database admin panel 
(Django2..6+Python3.6+Mysql5.7) where admin can operate create/edit/delete 
operations of database.
I am facing following IntegrityError  error when I try to Merge two 
products and click on Preview from my Django admin panel-
2018-07-02 16:17:56,428 [ERROR] exception.py:118 
handle_uncaught_exception() : Internal Server Error: 
/where2buy/merchantproduct/
Traceback (most recent call last):
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\django\db\backends\utils.py",
 
line 85, in _execute
return self.cursor.execute(sql, params)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\django\db\backends\mysql\base.py",
 
line 71, in execute
return self.cursor.execute(query, args)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\cursors.py",
 
line 250, in execute
self.errorhandler(self, exc, value)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\connections.py",
 
line 50, in defaulterrorhandler
raise errorvalue
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\cursors.py",
 
line 247, in execute
res = self._query(query)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\cursors.py",
 
line 411, in _query
rowcount = self._do_query(q)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\cursors.py",
 
line 374, in _do_query
db.query(q)
  File 
"C:\Users\prateek1.gupta\AppData\Local\Continuum\anaconda3\lib\site-packages\MySQLdb\connections.py",
 
line 277, in query
_mysql.connection.query(self, query)
_mysql_exceptions.IntegrityError: (1451, 'Cannot delete or update a parent 
row: a foreign key constraint fails (`productsearchv2`.`feed`, CONSTRAINT 
`feed_mproduct_id_fk` FOREIGN KEY (`merchant_id`, `merchant_product_id`) 
REFERENCES `merchant_product` (`merchant_id`, `merchant_product_id`) ON 
DELETE NO )')

I think issue is may be wrong relationship settings in my model file but 
couldn't able to find exact issue.
Can anyone please help me to find the issue? My code is as below-

class MerchantProduct(models.Model):
merchant = models.ForeignKey(Merchant, on_delete=models.CASCADE)
product = models.ForeignKey(Product, on_delete=models.SET_NULL, blank=True, 
null=True)
merchant_product_id = models.CharField(max_length=100)
gtin = models.CharField(max_length=15, blank=True, null=True)
merchant_group_id = models.CharField(max_length=100, blank=True, null=True)
name = models.CharField(max_length=300)
description = models.TextField(blank=True, null=True)
image_urls = models.TextField(blank=True, null=True)
image_phashes = models.TextField(blank=True, null=True)
web_url = models.URLField(blank=True, null=True)
brand = models.CharField(max_length=100, blank=True, null=True)
category = models.CharField(max_length=150, blank=True, null=True)
color = models.CharField(max_length=100, blank=True, null=True)
size = models.CharField(max_length=100, blank=True, null=True)
created_at = models.DateTimeField(auto_now_add=True, editable=False)
updated_at = models.DateTimeField(auto_now=True)

class Meta:
unique_together = (('merchant', 'merchant_product_id'),)
managed = False
db_table = 'merchant_product'

def __str__(self):
return self.name

class Product(models.Model):
merchants = models.ManyToManyField(Merchant, through='MerchantProduct')
brand = models.ForeignKey(Brand, related_name='brand', 
on_delete=models.SET_NULL, blank=True, null=True)
category = models.ForeignKey(Category, related_name='category', 
on_delete=models.SET_NULL, blank=True, null=True)
group = models.ForeignKey('self', related_name='ID', 
on_delete=models.SET_NULL, blank=True, null=True)
gtin = models.CharField(max_length=15, blank=True, null=True)
name = models.CharField(max_length=300)
description = models.TextField()
image_urls = models.TextField()
image_phashes = models.CharField(max_length=200, blank=True, null=True)
color = models.CharField(max_length=100, blank=True, null=True)
size = models.CharField(max_length=100, blank=True, null=True)
created_at = models.DateTimeField(auto_now_add=True, editable=False)
updated_at = models.DateTimeField(auto_now=True)

class Meta:
managed = False
db_table = 'product'

def __str__(self):
return self.name


class Merchant(models.Model):
DATA_QUALITY_CHOICES = (
('approx', 'Approximate'),
('exact', 'Exact'),
)
name = models.CharField(unique=True, max_length=45)
display_name = models.CharField(unique=True, max_length=255)
url_name = models.CharField(

Re: IntegrityError: FOREIGN KEY constraint failed: Django 2.0.3

2018-03-22 Thread Seven Reeds

Uh, am I not using the ORM?  If I am not then what must I do to get back on 
track?

I just realized that i didn't include the "Delete" CBV in my original 
post.  I do not have easy access to the code at the moment so what follows 
is a rough approximation of what that code is about and is prolly full of 
errors:

class Delete(DeleteView):
def get:
profile = Profile.objects.get(account_number=self.request.account_number)
user = user.objects.get(pk=profile.user.pk)
user.delete()

In a debugger I can stop on the "user.delete()" line and see that the 
profile and user objects are what I expect them to be.



On Wednesday, March 21, 2018 at 10:34:47 AM UTC-5, Simon Charette wrote:
>
> Hello Anon,
>
> Django doesn't use database level ON DELETE constraints and emulates them 
> in Python
> to dispatch pre_delete/post_delete signals. As long as you're using the 
> ORM to perform
> the deletion you shouldn't encounter constraint violations.
>
> There's a ticket to add support for database level on_delete 
> constraints[0].
>
> Cheers,
> Simon
>
> [0] https://code.djangoproject.com/ticket/21961
>
> Le mercredi 21 mars 2018 10:50:25 UTC-4, Anon Ymous a écrit :
>>
>> Hi,
>>
>> I am learning python by trying to create a small Django app.  I may have 
>> found a bug related to Django and/or sqlite3.  If you are stackoverflow 
>> folks then my initial post is there:  
>> https://stackoverflow.com/questions/49361834/integrityerror-exception-in-deleteview-cbv
>>
>> My app really is just creating a small web site to add users and figure 
>> out how to do CRUD operations in building user profiles.  I am using the 
>> following setup:
>>
>> Django Version: 2.0.3
>> Python Version: 3.6.3
>> Installed Applications:
>> ['django.contrib.admin',
>> 'django.contrib.auth',
>> 'django.contrib.contenttypes',
>> 'django.contrib.sessions',
>> 'django.contrib.messages',
>> 'django.contrib.staticfiles',
>> 'django_extensions',
>> 'django.contrib.sites',
>> 'allauth',
>> 'allauth.account',
>> 'allauth.socialaccount',
>> 'auditlog',
>> 'widget_tweaks',
>> 'Members.apps.MembersConfig']
>> Installed Middleware:
>> ['django.middleware.security.SecurityMiddleware',
>> 'django.contrib.sessions.middleware.SessionMiddleware',
>> 'django.middleware.common.CommonMiddleware',
>> 'django.middleware.csrf.CsrfViewMiddleware',
>> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>> 'django.contrib.messages.middleware.MessageMiddleware',
>> 'django.middleware.clickjacking.XFrameOptionsMiddleware',
>> 'auditlog.middleware.AuditlogMiddleware']
>>
>> I am using sqlite3 as the DB backend..
>>
>> I can create the virgin project, tweak the settings file and do the 
>> initial "makemigrations" and "migrate".  This, of course, creates the 
>> Django "user" table(s).  I went about creating my own "profile" model that 
>> "extends" the User model by creating a "oneToOne" field that points back to 
>> User and specifies an "on_delete=models.CASCADE" clause:
>>
>> class Profile(models.Model):
>> ...
>> user = models.OneToOneField(
>> User,
>> on_delete=models.CASCADE,
>> blank=False,
>> null=False,
>> )
>> ...
>>
>> The thing is the table that is created is given the constraint:
>>
>> FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) DEFERRABLE INITIALLY 
>> DEFERRED,
>>
>> but the "on delete cascade" clause is missing.  
>>
>> I first noticed this when testing a profile delete operation.  I get a 
>> foreign key constraint violation.  Looking into that led me here to you 
>> guys.
>>
>> I have added that clause to the table:
>>
>> FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) on delete cascade 
>> DEFERRABLE INITIALLY DEFERRED,
>>
>> but I still get the constraint violation.  I did more digging last night 
>> and see that at least one of the Django generated "user_*" tables also has 
>> a foreign key relationship back to the "user" table and that is also 
>> missing the cascade clause.
>>
>> My guesses at this instant include:
>>
>>- I have no idea what I am doing
>>- Django or the sqlite3 backend *should* be handling the cascade ops 
>>internally -- but isn't
>>
>> What am I missing?
>>
>

-- 
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/47509400-f086-4f25-b749-c5bf0853f2d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IntegrityError: FOREIGN KEY constraint failed: Django 2.0.3

2018-03-21 Thread Simon Charette

Hello Anon,

Django doesn't use database level ON DELETE constraints and emulates them 
in Python
to dispatch pre_delete/post_delete signals. As long as you're using the ORM 
to perform
the deletion you shouldn't encounter constraint violations.

There's a ticket to add support for database level on_delete constraints[0].

Cheers,
Simon

[0] https://code.djangoproject.com/ticket/21961

Le mercredi 21 mars 2018 10:50:25 UTC-4, Anon Ymous a écrit :
>
> Hi,
>
> I am learning python by trying to create a small Django app.  I may have 
> found a bug related to Django and/or sqlite3.  If you are stackoverflow 
> folks then my initial post is there:  
> https://stackoverflow.com/questions/49361834/integrityerror-exception-in-deleteview-cbv
>
> My app really is just creating a small web site to add users and figure 
> out how to do CRUD operations in building user profiles.  I am using the 
> following setup:
>
> Django Version: 2.0.3
> Python Version: 3.6.3
> Installed Applications:
> ['django.contrib.admin',
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'django_extensions',
> 'django.contrib.sites',
> 'allauth',
> 'allauth.account',
> 'allauth.socialaccount',
> 'auditlog',
> 'widget_tweaks',
> 'Members.apps.MembersConfig']
> Installed Middleware:
> ['django.middleware.security.SecurityMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.common.CommonMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> 'django.middleware.clickjacking.XFrameOptionsMiddleware',
> 'auditlog.middleware.AuditlogMiddleware']
>
> I am using sqlite3 as the DB backend..
>
> I can create the virgin project, tweak the settings file and do the 
> initial "makemigrations" and "migrate".  This, of course, creates the 
> Django "user" table(s).  I went about creating my own "profile" model that 
> "extends" the User model by creating a "oneToOne" field that points back to 
> User and specifies an "on_delete=models.CASCADE" clause:
>
> class Profile(models.Model):
> ...
> user = models.OneToOneField(
> User,
> on_delete=models.CASCADE,
> blank=False,
> null=False,
> )
> ...
>
> The thing is the table that is created is given the constraint:
>
> FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) DEFERRABLE INITIALLY 
> DEFERRED,
>
> but the "on delete cascade" clause is missing.  
>
> I first noticed this when testing a profile delete operation.  I get a 
> foreign key constraint violation.  Looking into that led me here to you 
> guys.
>
> I have added that clause to the table:
>
> FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) on delete cascade 
> DEFERRABLE INITIALLY DEFERRED,
>
> but I still get the constraint violation.  I did more digging last night 
> and see that at least one of the Django generated "user_*" tables also has 
> a foreign key relationship back to the "user" table and that is also 
> missing the cascade clause.
>
> My guesses at this instant include:
>
>- I have no idea what I am doing
>- Django or the sqlite3 backend *should* be handling the cascade ops 
>internally -- but isn't
>
> What am I missing?
>

-- 
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/0a368a90-da44-4af1-a5a1-d680e35d0b5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

IntegrityError: FOREIGN KEY constraint failed: Django 2.0.3

2018-03-21 Thread Anon Ymous

Hi,

I am learning python by trying to create a small Django app. I may have
found a bug related to Django and/or sqlite3. If you are stackoverflow
folks then my initial post is there:
https://stackoverflow.com/questions/49361834/integrityerror-exception-in-deleteview-cbv

My app really is just creating a small web site to add users and figure out
how to do CRUD operations in building user profiles. I am using the
following setup:

Django Version: 2.0.3
Python Version: 3.6.3
Installed Applications:
['django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django_extensions',
'django.contrib.sites',
'allauth',
'allauth.account',
'allauth.socialaccount',
'auditlog',
'widget_tweaks',
'Members.apps.MembersConfig']
Installed Middleware:
['django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'auditlog.middleware.AuditlogMiddleware']

I am using sqlite3 as the DB backend..

I can create the virgin project, tweak the settings file and do the initial
"makemigrations" and "migrate". This, of course, creates the Django "user"
table(s). I went about creating my own "profile" model that "extends" the
User model by creating a "oneToOne" field that points back to User and
specifies an "on_delete=models.CASCADE" clause:

class Profile(models.Model):
...
user = models.OneToOneField(
User,
on_delete=models.CASCADE,
blank=False,
null=False,
)
...

The thing is the table that is created is given the constraint:

FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) DEFERRABLE INITIALLY
DEFERRED,

but the "on delete cascade" clause is missing.

I first noticed this when testing a profile delete operation. I get a
foreign key constraint violation. Looking into that led me here to you
guys.

I have added that clause to the table:

FOREIGN KEY(`user_id`) REFERENCES `auth_user`(`id`) on delete cascade
DEFERRABLE INITIALLY DEFERRED,

but I still get the constraint violation. I did more digging last night
and see that at least one of the Django generated "user_*" tables also has
a foreign key relationship back to the "user" table and that is also
missing the cascade clause.

My guesses at this instant include:

- I have no idea what I am doing
- Django or the sqlite3 backend *should* be handling the cascade ops
internally -- but isn't

What am I missing?

--
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/29eb69c4-8f01-4695-b72e-0914ff46422e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: get_or_create IntegrityError

2017-02-16 Thread Vijay Khemlani

As far as I know Postgres uses "sequences" for generating the model IDs.

If you set the id manually I think you are bypassing the sequence,
which doesn't autoincrement. So when you use the sequence the next
time the ID clashes.

pgAdmin should auto generate the id if you leave the field blank.

On 2/16/17, Matthew Pava <matthew.p...@iss.com> wrote:
> This is a fascinating issue, fellow Django users.
>
> I have a model called Lookups that is basically just an auto-generated pk
> and a name.  I added some data to that table using pgAdmin 3 since I'm using
> a PostgreSQL backend.
> One of my users then filled out a form that ran some code that would
> 'get_or_create' on the Lookups model.  It threw an IntegrityError saying
> that the Key (id)=# already exists.
> Upon further investigation, I realized that the id # was one that I had
> already entered manually in the database several days ago.  Only after the
> user kept running that form until the id incremented to one that did not
> exist did the IntegrityError go away.
>
> Maybe I entered the id manually in pgAdmin 3 instead of letting it do the
> auto-generation and that's why it broke?
>
> But Django was generating the proper SQL, so I can't imagine how Django
> could possibly be involved in addressing this issue:
>
> 'INSERT INTO "general_lookups" ("name") VALUES (%s) RETURNING
> "general_lookups"."id"'
>
>
> Maybe it's more a problem with PostgreSQL, but I wanted to share this with
> you in case you ever run into this issue.  I think for now, I should just
> use Django to enter data into the database, or test pgAdmin to
> auto-increment the id with manual data entry.
>
> --
> 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/5d108192354c470ca56946d28ffe02b7%40ISS1.ISS.LOCAL.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALn3ei3ZjhY%2BYfZyJUzZamA8t1t3JUw37_mGm%2BY4ymFG%2Bq%3D7Cw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

get_or_create IntegrityError

2017-02-16 Thread Matthew Pava

This is a fascinating issue, fellow Django users.

I have a model called Lookups that is basically just an auto-generated pk and a
name. I added some data to that table using pgAdmin 3 since I'm using a
PostgreSQL backend.
One of my users then filled out a form that ran some code that would
'get_or_create' on the Lookups model. It threw an IntegrityError saying that
the Key (id)=# already exists.
Upon further investigation, I realized that the id # was one that I had already
entered manually in the database several days ago. Only after the user kept
running that form until the id incremented to one that did not exist did the
IntegrityError go away.

Maybe I entered the id manually in pgAdmin 3 instead of letting it do the
auto-generation and that's why it broke?

But Django was generating the proper SQL, so I can't imagine how Django could
possibly be involved in addressing this issue:

'INSERT INTO "general_lookups" ("name") VALUES (%s) RETURNING
"general_lookups"."id"'

Maybe it's more a problem with PostgreSQL, but I wanted to share this with you
in case you ever run into this issue. I think for now, I should just use
Django to enter data into the database, or test pgAdmin to auto-increment the
id with manual data entry.

--
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/5d108192354c470ca56946d28ffe02b7%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Re: IntegrityError column email is not unique

@James

As per my understanding I did following. Now it is not adding email if it 
exists but also its not giving me any error.

class GuestCheckoutForm(forms.Form):
email = forms.EmailField()
email2 = forms.EmailField(label='Verify Email')

def clean_email(self):
email = self.cleaned_data["email"]
if UserCheckout.objects.filter(email=email).exists():
raise forms.ValidationError("Please confirm emails addresses 
are the same.")
return email

def clean(self):
cleaned_data = super(GuestCheckoutForm, self).clean()
email = cleaned_data.get('email')
email2 = cleaned_data.get('email2')

if email and email2 and email != email2:
self.add_error('email2', forms.ValidationError('Please confirm 
emails addresses.'))

Rest of the code is same.

-- 
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/a63b8508-063d-405c-a7a2-67ab428bea21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IntegrityError column email is not unique

@James

As per my understanding I did following. Now it is not adding email if it 
exists but also its not giving me any error.

class GuestCheckoutForm(forms.Form):
email = forms.EmailField()
email2 = forms.EmailField(label='Verify Email')

def clean_email(self):
email = self.cleaned_data["email"]
if UserCheckout.objects.filter(email=email).exists():
raise forms.ValidationError("Please confirm emails addresses 
are the same.")
return email

def clean(self):
cleaned_data = super(GuestCheckoutForm, self).clean()
email = cleaned_data.get('email')
email2 = cleaned_data.get('email2')

if email and email2 and email != email2:
self.add_error('email2', forms.ValidationError('Please confirm 
emails addresses.'))

Rest of the code is same.

-- 
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/12116f4b-01b5-4a33-9397-20819d11557d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IntegrityError column email is not unique

Thanks james for your kind response.
Intention is to set a single identifier for guest user account email. If 
that email exists then user can login or if doesn't he will have to get 
registered.
However let me implement your suggested code and I will respond you back.

Thanks again

-- 
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/a9ffd1b7-cd56-4cf6-853f-66409c700074%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IntegrityError column email is not unique

2016-07-02 Thread James Schneider

On Jul 2, 2016 7:23 AM, "M Hashmi" <mhashmi1...@gmail.com> wrote:
>
> I am working on my Checkout view with regular/guest user but getting hard
time to come around the integrity error. Idea is to let guest users
register with email only to checkout and I need to set the user email
unique.
>
> models.py
>
> from django.conf import settings
> from django.db import models
>
> class UserCheckout(models.Model):
> user = models.OneToOneField(settings.AUTH_USER_MODEL, null=True,
blank=True)
> email = models.EmailField(unique=True)
>
> def __unicode__(self):
> return self.email
>
>
> forms.py
>
>
>
>
> from django import forms
> from django.contrib.auth import get_user_model
>
> User=get_user_model()
> class GuestCheckoutForm(forms.Form):
> email = forms.EmailField()
> email2 = forms.EmailField(label='Verify Email')
> def clean_email2(self):
> email = self.cleaned_data.get("email")
> email2 = self.cleaned_data.get("email2")
> if email == email2:
> user_exists = User.objects.filter(email=email).count()
> if user_exists != 0:

This should probably be

if UserCheckout.objects.filter(email=email).exists():

Do not use count() for checking whether or not a record exists. You are
also checking against User objects, and not against UserCheckout objects,
which doesn't make any sense based on the code you've posted.

> raise forms.ValidationError("User already exists. Please
login instead")
> return email2
> else:
> raise forms.ValidationError("Please confirm emails addresses
are the same.")
>
>
> In my cart views this is how I've rendered my form.
>
>
> def post(self, request, *args, **kwargs):
> self.object = self.get_object()
> form = self.get_form()
> if form.is_valid():
> email = form.cleaned_data.get("email")
> user_checkout = UserCheckout.objects.create(email=email)

Here is where the actual error is coming from. Your validation only checks
User for a unique email constraint, but then you create a UserCheckout
object without first checking the unique email constraint for UserCheckout.

> return self.form_valid(form)
> else:
> return self.form_invalid(form)
>
>
> I've registered the model with admin and in admin it shows the error for
duplication perfectly fine but from frontend I am getting error below:
>
>
> IntegrityError at /checkout/
> column email is not unique
> Request Method: POST
> Request URL:http://localhost:8000/checkout/
> Django Version: 1.8.13
> Exception Type: IntegrityError
> Exception Value:
> column email is not unique
> Exception Location:
C:\Users\Ali\ecomm\lib\site-packages\django\db\backends\sqlite3\base.py in
execute, line 318
> Python Executable:  C:\Users\Ali\ecomm\Scripts\python.EXE
> Python Version: 2.7.9
>

You'll only get this error if a user checks out using an email address that
matches an existing user, not an existing email that's been used to check
out before.

Is the intention to create both UserCheckout and User objects (which can
log in) through this process?

-James

-- 
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/CA%2Be%2BciVbUJ_P0jFAeybUZPifEsbO7sE%3Dz%3DSU9%2BACdfDb_PX49g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

IntegrityError column email is not unique