#31607: Subquery.__eq__() doesn't work properly for resolved subqueries.
-------------------------------------+-------------------------------------
     Reporter:  felixxm              |                    Owner:  felixxm
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    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:"d5231719e0ec86dc6b71487e5461b34bac1c55f6" d5231719]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5231719e0ec86dc6b71487e5461b34bac1c55f6"
 [3.1.x] Refs #31607 -- Added release notes for
 a125da6a7c79b1d4c55677d0bed6f9b1d7d77353.

 Backport of 8328811f048fed0dd22573224def8c65410c9f2e from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31607#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ff50d046aa2c00a1f3593594bb6b1cc7%40djangoproject.com.

Reply via email to