#31568: Alias used in aggregate filtering is incorrect.
-------------------------------------+-------------------------------------
Reporter: Gagaro | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Gagaro):
Replying to [comment:1 Simon Charette]:
> Thank you for your report. Did you manage to reproduce against Django
3.0.5 as well? If it's the case could you try reducing your model set and
queryset interactions to a minimal that still trigger the issue. That'll
help tremendously in reproducing the regression and ensure it gets
addressed in a timely manner. Thanks!
I tried to reduce it as much as I could in my context without having to
try with whole new models. Do you still need me to do that as felixxm
apparently was able to reproduce it?
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/31568#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.75bbfdef5a286789aae8d03a69b20e69%40djangoproject.com.
