#35586: Aggregation optimization doesn't account for not referenced
set-returning
annotations on Postgres
-------------------------------------+-------------------------------------
Reporter: Devin Cox | Owner: Devin Cox
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: postgres, set- | Triage Stage: Ready for
returning, aggregation, | checkin
annotation |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"e03083917db03757e48f8edac4c8491b72c8a3c4" e030839]:
{{{#!CommitTicketReference repository=""
revision="e03083917db03757e48f8edac4c8491b72c8a3c4"
Fixed #35586 -- Added support for set-returning database functions.
Aggregation optimization didn't account for not referenced set-returning
annotations on Postgres.
Co-authored-by: Simon Charette <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35586#comment:14>
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/0107019146ccff7d-9c988ef2-b26f-4408-a755-8483bb604761-000000%40eu-central-1.amazonses.com.
