#27412: Coalesce function should work with subqueries
-------------------------------------+-------------------------------------
Reporter: Tzu-ping Chung | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson <carlton@…>):
In [changeset:"b30c0081d4d8a31ab7dc7f72a4c7099af606ef29" b30c0081]:
{{{
#!CommitTicketReference repository=""
revision="b30c0081d4d8a31ab7dc7f72a4c7099af606ef29"
Refs #27412 -- Confirmed support for executing Coalesce(subquery).
This has been supported for subqueries wrapped in Subquery since the
expression
was introduced and for Queryset directly since Subquery resolves to
sql.Query.
Piggy-backed on the existing tests covering Coalesce handling of
EmptyResultSet
as it seemed like a proper location to combine testing.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27412#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/01070182cf67c461-9bc59c37-c734-441b-8e44-f23fa97cfc2e-000000%40eu-central-1.amazonses.com.
