#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
-------------------------------------+-------------------------------------
Comment (by Ionel Cristian Mărieș):
Whoops, I misreported what triggers this. The error is the same but it's
not create, it's full_clean:
{{{
Schedule(start_time=time(2), end_time=time(1)).full_clean()
}}}
In 3.2 that raised a ValidationError
In 4.2 it raises that DataError
I'd expect this would create nasty 500 error responses in form processing.
Correct me if I'm wrong.
Still need a way to deal with this, otherwise I can't upgrade to 4.2.
--
Ticket URL: <https://code.djangoproject.com/ticket/34293#comment:2>
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/01070185eb4d4222-66fa8686-57a9-4c8d-8312-16aea9b4dfdc-000000%40eu-central-1.amazonses.com.
