#33018: Incorrect annotation value when doing a subquery with empty queryset
-------------------------------------+-------------------------------------
Reporter: decomorreno | Owner: David
| Wobrock
Type: Bug | Status: assigned
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: orm, annotate, | Triage Stage: Accepted
EmptyQuerySet, empty, count |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Wobrock):
* cc: David Wobrock (added)
* owner: nobody => David Wobrock
* has_patch: 0 => 1
* status: new => assigned
Comment:
Hi!
Thanks for the hints Simon, I tried a first patch where we catch empty
values here https://github.com/django/django/pull/14770
Should we expand the solution a bit further and rename
`empty_aggregate_value` as you suggested, and use it in the `SQLCompiler`
too?
--
Ticket URL: <https://code.djangoproject.com/ticket/33018#comment:3>
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.dbadd5aedf73a36b1a089d239cec2528%40djangoproject.com.
