#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):
Hi Claude. Good. I think "Regressions" here and in the
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions] docs isn't quite clear: it should
say "Regressions introduced since the last release" — that's how it's been
applied that I've seen, and I think it's also
[https://groups.google.com/d/topic/django-
developers/P4Vsa8zqFyo/discussion the historical intention]. (Guess but, I
suspect widening that might lead us to the land of several hundred release
blockers.) I shall propose a small edit to the docs.
Having discussed with Mariusz, we're happy to backport this fix. It's
similar enough to #30315, and is a quite central use-case.
--
Ticket URL: <https://code.djangoproject.com/ticket/31097#comment:24>
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.33e2910aa4cc0d77d241f9b2fd5b9864%40djangoproject.com.
