#25171: Can't update queryset after Count annotation
-------------------------------------+-------------------------------------
Reporter: fraserharris | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset, update, | Triage Stage: Accepted
annotate, count |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by carljm):
* stage: Unreviewed => Accepted
Comment:
Replying to [comment:2 timgraham]:
> I guess trying to update after annotations or aggregations probably
isn't designed to work. Should we throw a friendlier error message?
Well, certainly not after a terminal aggregation. But I don't see any a
priori reason to assume that if you have an annotated `QuerySet` you
shouldn't be able to update it. ISTM this should be accepted as a bug, and
we should only resort to "friendlier error message" if somebody looks at
it closely and reports more authoritatively that it's not feasible to
support.
--
Ticket URL: <https://code.djangoproject.com/ticket/25171#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/070.4af152a36dec1a35ad05245199782187%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
