#30052: QuerySet.only() doesn't support annotations
-------------------------------------+-------------------------------------
Reporter: Kal Sze | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Kal Sze):
Replying to [comment:1 Tim Graham]:
> As far as I tested, annotations don't need to be included in `only()` in
order to be included in the query. The documentation for `only()` and
`defer()` only discuss using it with fields, not with annotations.
I know it doesn't need to be included, but I thought the point of `only()`
and `defer()` is to exclude the fields that we are not interested in, when
executing the initial database query. Having `only()` support annotations
is useful if I'm only interested in the annotated field, and not in the
regular fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/30052#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.bd5317ad6e2261dc448faa3b9515307c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
