I notice there are a few aggregates now that support Distinct (Count,
StringAgg and hopefully ArrayAgg). It might be good to make a subclass
they inherit from, instead of duplicating the implementation?
If this is deemed a good idea I can add some documentation changes and any
changes that are requested.
--
Ticket URL: <https://code.djangoproject.com/ticket/27767>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_docs: 0 => 1
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
> I notice there are a few aggregates now that support Distinct (Count,
StringAgg and hopefully ArrayAgg). It might be good to make a subclass
they inherit from, instead of duplicating the implementation?
Makes sense to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/27767#comment:1>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/27767#comment:2>
* needs_better_patch: 1 => 0
* needs_docs: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/27767#comment:3>
* owner: (none) => Tim Graham <timograham@…>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b5393028bfc939adf14d0fa5e4088cddd3b9dfa1" b5393028]:
{{{
#!CommitTicketReference repository=""
revision="b5393028bfc939adf14d0fa5e4088cddd3b9dfa1"
Fixed #27767 -- Added distinct argument to ArrayAgg.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27767#comment:4>