#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:"0ba5aadb3377e49e995753944a7e5e55c3840bed" 0ba5aadb]:
{{{
#!CommitTicketReference repository=""
revision="0ba5aadb3377e49e995753944a7e5e55c3840bed"
[3.0.x] Fixed #31607 -- Fixed evaluated Subquery equality.
Regression in 691def10a0197d83d2d108bd9043b0916d0f09b4.
Backport of a125da6a7c79b1d4c55677d0bed6f9b1d7d77353 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31607#comment:5>
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.d485d815626977c417bf934ece38d386%40djangoproject.com.
