#33829: BaseConstraint.deconstruct() and __eq__ operators don't take
violation_error_message into account.
-------------------------------------+-------------------------------------
     Reporter:  Mariusz Felisiak     |                    Owner:  Stéphane
                                     |  "Twidi" Angel
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  4.1
  (models, ORM)                      |
     Severity:  Release blocker      |               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 Mariusz Felisiak <felisiak.mariusz@…>):

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


Comment:

 In [changeset:"ccbf714ebeff51d1370789e5e487a978d0e2dbfb" ccbf714]:
 {{{
 #!CommitTicketReference repository=""
 revision="ccbf714ebeff51d1370789e5e487a978d0e2dbfb"
 Fixed #33829 -- Made BaseConstraint.deconstruct() and equality handle
 violation_error_message.

 Regression in 667105877e6723c6985399803a364848891513cc.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33829#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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181dc994ecd-82bba2f0-65dc-4a47-9411-3398c6d296be-000000%40eu-central-1.amazonses.com.

Reply via email to