#29868: Database constraint checks are not retained on sqlite
-------------------------------------+-------------------------------------
     Reporter:  Scott Stevens        |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:  check constraint     |             Triage Stage:  Ready for
  sqlite                             |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton.gibson@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"95bda03f2da15172cf342f13ba8a77c007b63fbb" 95bda03]:
 {{{
 #!CommitTicketReference repository=""
 revision="95bda03f2da15172cf342f13ba8a77c007b63fbb"
 Fixed #29868 -- Retained database constraints on SQLite table rebuilds.

 Refs #11964.

 Thanks Scott Stevens for testing this upcoming feature and the report.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29868#comment:7>
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.643a6b8d5465ca4c3cd22165f8624ddb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to