#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-------------------------------------+-------------------------------------
Reporter: Laurent Tramoy | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: contrib.postgres | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Tim beat me with a stick plenty of times when I was starting :) — Data
loss bugs and security issues to all supported versions. Regressions and
bugs in new features to current main version. I did think we should be
more liberal but backporting itself isn't risk free, so the more I see it
the more I think this is correct.
A change would be a change in policy though so we'd need to go via the
discussion group and technical board I think.
--
Ticket URL: <https://code.djangoproject.com/ticket/31097#comment:22>
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.3de542a44d3c19fbd330204d5e2aa0fa%40djangoproject.com.
