#34078: Add Postgres range_merge aggregate function to postgres.contrib
-------------------------------------+-------------------------------------
Reporter: Jack Linke | Owner: (none)
Type: New feature | Status: new
Component: contrib.postgres | Version: 4.1
Severity: Normal | Resolution:
Keywords: postgres range | Triage Stage:
range_merge aggregation aggregate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
I think adding the `range_merge` function could be accepted in
contrib.postgres. However, what you suggest is to add a custom aggregate
(which is a different variant of the `range_agg`/`range_intersect_agg`
aggregations added in PostgreSQL 14). Therefore, my opinion is that your
custom aggregation is quite niche and could stay in a custom package.
--
Ticket URL: <https://code.djangoproject.com/ticket/34078#comment:2>
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/01070183be6e1648-024c1a56-52c9-4f96-a1e0-4bbc8af490fe-000000%40eu-central-1.amazonses.com.
