| Age | Commit message (Collapse) | Author |
|
|
|
contrib.postgres.aggreggates.StringAgg.delimiter.
|
|
docs/ref/contrib/postgres/aggregates.txt.
|
|
|
|
deprecation timeline.
|
|
|
|
This moves the behaviors of `order_by` used in Postgres aggregates into
the `Aggregate` class. This allows for creating aggregate functions that
support this behavior across all database engines. This is shown by
moving the `StringAgg` class into the shared `aggregates` module and
adding support for all databases. The Postgres `StringAgg` class is now
a thin wrapper on the new shared `StringAgg` class.
Thank you Simon Charette for the review.
|
|
|
|
Aligns the argument with SQL standards already used in Window.order_by and
sets up for adding support to Aggregate.
|
|
This also removes remaining versionadded/changed annotations for older
versions.
|
|
|
|
Thanks to J.V. Zammit, Paolo Melchiorre, and Mariusz Felisiak for
reviews.
|
|
Per deprecation timeline.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
JSONBAgg results.
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
|
This deprecates forcing a return value for ArrayAgg, JSONBAgg, and
StringAgg when there are no rows in the query. Now that we have a
``default`` argument for aggregates, we want to revert to returning the
default of ``None`` which most aggregate functions return and leave it
up to the user to decide what they want to be returned by default.
|
|
Thanks to Simon Charette and Adam Johnson for the reviews.
|
|
|
|
aggregate functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks to Christian von Roques for the report.
|
|
|
|
Thanks Tim Graham for review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|