#35103: UniqueConstraint message does not use violation_error_message
-------------------------------------+-------------------------------------
Reporter: Gerben Morsink | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: UniqueConstraint, | Triage Stage: Accepted
violation_error_message |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* has_patch: 1 => 0
* ui_ux: 1 => 0
* stage: Unreviewed => Accepted
Comment:
While Simon did provide a draft patch on the forum, I'll uncheck "Has
patch" until there is a pull request to review.
--
Ticket URL: <https://code.djangoproject.com/ticket/35103#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cf94738fe-95f12060-4a00-4d65-a421-aca87f0394ba-000000%40eu-central-1.amazonses.com.
