#34293: Extra validation introduced in 30581 breaks certain constraint setups
-------------------------------------+-------------------------------------
Reporter: Ionel Cristian | Owner: nobody
Mărieș |
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
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: => invalid
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => Bug
Comment:
`.create()` doesn't automatically call constraints validation, so it
behaves exactly the same in both Django 3.2 and 4.2a1 and crashes with
`IntegrityError`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34293#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070185eacf49a6-05492f1a-e308-4b86-80e7-c95bdf68fb81-000000%40eu-central-1.amazonses.com.
