#11964: Add the ability to use database-level CHECK CONSTRAINTS
-------------------------------------+-------------------------------------
Reporter: Matthew Schinckel | Owner: Ian Foote
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: check constraint | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"9142bebff2657f2129a2028137f81d09db989968" 9142bebf]:
{{{
#!CommitTicketReference repository=""
revision="9142bebff2657f2129a2028137f81d09db989968"
Refs #11964 -- Changed CheckConstraint() signature to use keyword-only
arguments.
Also renamed the `constraint` argument to `check` to better represent
which
part of the constraint the provided `Q` object represents.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/11964#comment:34>
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.49faa21816fe3d6e56daea5f856b8c90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
