#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:5 Mariusz Felisiak]:
> > 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.
I am not getting any errors at all, I get the green success message that
the object was created successfully. I tried this on different models and
got the same behavior. I dont know why were not able to reproduce this.
--
Ticket URL: <https://code.djangoproject.com/ticket/33907#comment:7>
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/0107018282f22e9b-75c5e8ef-3506-4f49-884f-091aed6f3a80-000000%40eu-central-1.amazonses.com.