#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 -------------------------------------+------------------------------------- Changes (by Tim Graham <timograham@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"952f05a6db2665d83c04075119285f2164b03432" 952f05a6]: {{{ #!CommitTicketReference repository="" revision="952f05a6db2665d83c04075119285f2164b03432" Fixed #11964 -- Added support for database check constraints. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/11964#comment:31> 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/067.d95acb3611a0bad7eeb2f3d94d86ad6e%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.