#35103: UniqueConstraint message does not use violation_error_message
-------------------------------------+-------------------------------------
Reporter: Gerben Morsink | Owner: Gerben
Type: | Morsink
Cleanup/optimization | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: UniqueConstraint, | Triage Stage: Ready for
violation_error_message | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: new => closed
Comment:
In [changeset:"e970bb7ca71c00594b42a024a15a8ac007cc2c7a" e970bb7]:
{{{#!CommitTicketReference repository=""
revision="e970bb7ca71c00594b42a024a15a8ac007cc2c7a"
Fixed #35103 -- Used provided error code and message when fields is set
without a condition on UniqueConstraint.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35103#comment:19>
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/01070192754d2f09-cd3acd76-9367-42c4-9824-3decc4c5555d-000000%40eu-central-1.amazonses.com.
