#10199 closed (fixed)
aggregate method on queryset shouldn't alter the state of the queryset
| Reported by: | Alex Gaynor | Owned by: | Alex Gaynor |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
basically it should clone the query so as not to affect the queryset for future usage, I'll post a testcase shortly.
Attachments (1)
Change History (4)
by , 15 years ago
| Attachment: | aggregation-clone.diff added |
|---|
comment:1 by , 15 years ago
| Has patch: | set |
|---|---|
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 11 years ago
| Component: | ORM aggregation → Database layer (models, ORM) |
|---|
Note:
See TracTickets
for help on using tickets.
(In [9819]) Fixed #10199 -- Modified aggregate() calls to clone the base query so that the base query can be reused. Thanks to Alex Gaynor for the report and patch.