Re: [Django] #33907: UniqueConstraints voided when using GenericTabularInline (was: Uniqueconstraints voided in when using GenericTabularInline)

[Django]

#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => needsinfo
* severity: Release blocker => Normal

Comment:

> However creating the same object through GenericTabularInline gives no
errors and the creation is successful when it should not be. So basically
Useconstraints is not working at all with GenericTabularInline.

I cannot reproduce this issue, it crashes for me (as expected) with:
{{{
UNIQUE constraint failed: test_one_skill_level.user_id,
test_one_skill_level.content_type_id, test_one_skill_level.object_id
}}}

If you're also getting `IntegrityError` than it's a duplicate of #13091.

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