#30621: CheckConstraint crash with __contains lookup on DateTimeRangeFields.
-------------------------------------+-------------------------------------
     Reporter:  Tilman Koschnick     |                    Owner:  felixxm
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  2.2
  (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 GitHub <noreply@…>):

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


Comment:

 In [changeset:"7991111af12056ec9a856f35935d273526338c1f" 7991111]:
 {{{
 #!CommitTicketReference repository=""
 revision="7991111af12056ec9a856f35935d273526338c1f"
 Fixed #30621 -- Fixed crash of __contains lookup for
 Date/DateTimeRangeField when the right hand side is the same type.

 Thanks Tilman Koschnick for the report and initial patch.
 Thanks Carlton Gibson the review.

 Regression in 6b048b364ca1e0e56a0d3815bf2be33ac9998355.
 }}}

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

Reply via email to