#30315: StringAgg with ordering in subquery generates invalid string_agg() SQL
function call
-------------------------------------+-------------------------------------
Reporter: Reupen Shah | Owner: Caio
| Ariede
Type: Bug | Status: closed
Component: contrib.postgres | Version: 2.2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"1172f078eb04e0125413b061d3ccf7a283993b89" 1172f078]:
{{{
#!CommitTicketReference repository=""
revision="1172f078eb04e0125413b061d3ccf7a283993b89"
[2.2.x] Fixed #30315 -- Fixed crash of ArrayAgg and StringAgg with
ordering when used in Subquery.
Backport of a3f91891d2c7f4bdc33f48ae70820ef6f36da26e from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30315#comment:9>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c6114ff09b1c4984e6b7424817a742f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
