#33907: UniqueConstraints voided when using GenericTabularInline
-------------------------------------+-------------------------------------
     Reporter:  Mohamed Alnahhas     |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:                       |                  Version:  4.1
  contrib.contenttypes               |
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mohamed Alnahhas):

 Replying to [comment:4 Simon Charette]:
 > I didn't test it out but assume this is happening because
 `GenericTabularInline`'s form is passing an `exclude` of either
 `{'user','content_type', 'object_id'}` the following statement confused me
 though
 >
 > > However creating the same object through GenericTabularInline gives no
 errors and the creation is successful when it should not be.
 >
 > How is this possible, isn't the database crashing due a unique
 constraint violation?
 >
 > Can you also reproduce the same issue by using `unique_together` instead
 of `UniqueConstraint(fields=['user','content_type', 'object_id'],
 name='unique_object')`. If you can then I'm not convinced this should be
 considered a release blocker.

 It is not crashing, the object is created successfully and I get the green
 success message I can even go to the Skill_level admin page and see the
 duplicate objects. Opening one of the objects and saving without any
 changes gives the usual Uniqueconstraints error message.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33907#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018282ef9191-2eb9b50b-0d9e-4ca2-89f6-694d6bf70a9f-000000%40eu-central-1.amazonses.com.

Reply via email to