#33018: Incorrect annotation value when doing a subquery with empty queryset
-------------------------------------+-------------------------------------
Reporter: decomorreno | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: orm, annotate, | Triage Stage: Ready for
EmptyQuerySet, empty, count | 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:"dd1fa3a31b4680c0d3712e6ae122b878138580c7" dd1fa3a3]:
{{{
#!CommitTicketReference repository=""
revision="dd1fa3a31b4680c0d3712e6ae122b878138580c7"
Fixed #33018 -- Fixed annotations with empty queryset.
Thanks Simon Charette for the review and implementation idea.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33018#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.0e830df394c742d69ed2e2992d37c001%40djangoproject.com.
