#35275: Constraints validation fails on UniqueConstraint using OpClass
-------------------------------------+-------------------------------------
     Reporter:  Mathieu Kniewallner  |                    Owner:  Mariusz
                                     |  Felisiak
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             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 Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"f030236a86a64a4befd3cc8093e2bbeceef52a31" f030236a]:
 {{{#!CommitTicketReference repository=""
 revision="f030236a86a64a4befd3cc8093e2bbeceef52a31"
 Fixed #35275 -- Fixed Meta.constraints validation crash on
 UniqueConstraint with OpClass().

 This also introduces Expression.constraint_validation_compatible that
 allows specifying that expression should be ignored during a constraint
 validation.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35275#comment:6>
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/0107018f763d3dca-6bf71493-56fa-42ea-ae2b-9f974e38631a-000000%40eu-central-1.amazonses.com.

Reply via email to