#27021: Add explicit support for Q object annotations
-------------------------------------+-------------------------------------
Reporter: Josh Smeaton | Owner: Ian Foote
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| 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:"f42ccdd835e5b3f0914b5e6f87621c648136ea36" f42ccdd8]:
{{{
#!CommitTicketReference repository=""
revision="f42ccdd835e5b3f0914b5e6f87621c648136ea36"
Fixed #27021 -- Allowed lookup expressions in annotations, aggregations,
and QuerySet.filter().
Thanks Hannes Ljungberg and Simon Charette for reviews.
Co-authored-by: Mariusz Felisiak <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27021#comment:17>
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/066.4ff66927f43d8f51ae25c22ef4c57efe%40djangoproject.com.