#35586: Aggregation optimization doesn't account for not referenced
set-returning
annotations on Postgres
-------------------------------------+-------------------------------------
Reporter: Devin Cox | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres, set- | Triage Stage: Accepted
returning, aggregation, |
annotation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Devin Cox):
Went ahead and implemented/tested your suggestions and they work great for
our individual use case. Also pushed a PR for this. I know there may be
additional items now within the scope, such as support for `Unnest`, but I
wanted to go ahead and get the ball rolling. Also will need to add
documentation for this. Let me know if there are other ways I can help.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/35586#comment:8>
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/01070190eb45383c-0ba70c56-6c79-492e-b3de-129a110103bd-000000%40eu-central-1.amazonses.com.
