#10060: Multiple table annotation failure
-------------------------------------+-------------------------------------
Reporter: svsharma@… | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam M. Costello):
* cc: Adam M. Costello (added)
Comment:
Does anyone here understand roughly what is safe to do with annotate()?
If I call annotate() only once on a queryset, with only one argument, is
that always safe, no matter how many relationships I follow in annotate()
and filter()?
Is it safe to pass multiple arguments to annotate() (or call annotate()
multiple times) if none of the annotations follow any relationships? Even
if there are relationships followed inside filter()?
Do the problems with annotate() also apply to aggregate(), or is it safe
to pass multiple arguments to aggregate() ? Is it safe to call annotate()
with one argument and then call aggregate()?
--
Ticket URL: <https://code.djangoproject.com/ticket/10060#comment:65>
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/081.9308bc2e5441bf5fc2241307f8b14f03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
