#26430: Coalesce in Aggregations ignored when EmptyResultSet returned
-------------------------------------+-------------------------------------
Reporter: ryanprater | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution:
Keywords: aggregation | Triage Stage:
coalesce in queryset | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
I agree with Josh that the `on_empty_result` approach seems like a lot of
work for very little gain but I can't see any other way to fix this issue
appropriately.
@ryanprater not throwing `EmptyResultSet` in the `In` lookup would solve
your particular issue but the underlying one would remain, using
`Coalesce` with aggregation can result in an unexpected return value as
`EmptyResultSet` is thrown by other part of Django (`queryset.none()`
relies on it).
--
Ticket URL: <https://code.djangoproject.com/ticket/26430#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c978e700d65e4f280ec11067d18c2a2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
