#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 Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"8b3e1b6e9e4ee87fe85b2e5437faf59457e03e62" 8b3e1b6]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b3e1b6e9e4ee87fe85b2e5437faf59457e03e62"
 Refs #11964 -- Made constraint support check respect required_db_features.

 This will notably silence the warnings issued when running the test
 suite on MySQL.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/11964#comment:41>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.89255ae6270cc0bf7423a797a17b9a94%40djangoproject.com.

Reply via email to