#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
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"1088a9777da86dbf398106761c776edab29b163b" 1088a977]:
 {{{
 #!CommitTicketReference repository=""
 revision="1088a9777da86dbf398106761c776edab29b163b"
 [2.2.x] 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 for the review.

 Regression in 6b048b364ca1e0e56a0d3815bf2be33ac9998355.
 Backport of 7991111af12056ec9a856f35935d273526338c1f from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30621#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.bc64fc9ad642ee3df9db14afafa1e440%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to