#30062: Add UniqueConstraint condition parameter
-------------------------------------+-------------------------------------
Reporter: Pavel Tyslacki | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* has_patch: 1 => 0
Old description:
> According [https://code.djangoproject.com/ticket/29641] and
> [https://code.djangoproject.com/ticket/29547] add support of conditional
> unique constraint.
>
> Postgresql and sqlite support it as unique index: `CREATE UNIQUE INDEX
> ... WHERE condition`, for unsupported databases this constraint will not
> be applied at all.
New description:
According #29641 and #29547, add support of conditional unique constraint.
Postgresql and sqlite support it as unique index: `CREATE UNIQUE INDEX ...
WHERE condition`, for unsupported databases this constraint will not be
applied at all.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/30062#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.97cdb9cf5c023578c39f139e6be8f000%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
