#35910: Use violation_error_message on UniqueContraint when only fields and no
constraint is provided
-------------------------------------+-------------------------------------
Reporter: James Walters | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version:
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: forms, models, | Triage Stage:
unique constraints | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by James Walters):
Ah! This would be it. Sorry, looked to see if someone had already ran into
this but didn't come across that ticket. Happy to see it fixed!
--
Ticket URL: <https://code.djangoproject.com/ticket/35910#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 visit
https://groups.google.com/d/msgid/django-updates/0107019327333ff6-34698c66-9cbe-4922-a0fe-f4d28854dedc-000000%40eu-central-1.amazonses.com.
