#29641: Add support for unique constraints to Meta.constraints
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Ian Foote
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"db13bca60a6758d5fe63eeb01c00c3f54f650715" db13bca6]:
{{{
#!CommitTicketReference repository=""
revision="db13bca60a6758d5fe63eeb01c00c3f54f650715"
Fixed #29641 -- Added support for unique constraints in Meta.constraints.
This constraint is similar to Meta.unique_together but also allows
specifying a name.
Co-authored-by: Ian Foote <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29641#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.5dc6831226eea449c4a824dbe308fc76%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
