#35339: Ordering and filtering a Postgres ArrayAgg with parameters inverts SQL
param order
-------------------------------------+-------------------------------------
Reporter: Chris M | Owner: Chris M
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres arrayagg | Triage Stage: Accepted
ordering |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Sounds good! I suggest you start by making both `Aggregate` and
`OrderableAggMixin` unconditionally return `None` in their
`source_expressions` getters and setters when they respectively don't have
any `filter` and `ordering`.
This should address the immediate issue reported in this ticket and from
there, if you're feeling confident, merging `OrderableAggMixin` and
dealing with its deprecation could be tackled in a follow up ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/35339#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e9b00cb6b-a46d3178-9531-4620-927b-253d587822e6-000000%40eu-central-1.amazonses.com.
