#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 Gavin Wahl):
Is it now possible to define a field that comes with a check constraint,
or can they only be defined at the table level? I'd like to be able to
define my own StrictlyPositiveIntegerField.
--
Ticket URL: <https://code.djangoproject.com/ticket/11964#comment:32>
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.4a4776a0fe21d8b302d1766f6d072e7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
