We have room for some improvement here. It should be possible to add
subqueries to the current query. This would be especially useful for
adding aggregates.
For aggregates we need this feature because the current API doesn't
work for anything but simple cases. For example
Book.objects.annotate(aut
Thanks Simon and Tim,
I'd be ok with moving them into the tests in 1.10, but would give people a
bit more time to see and respond to this discussion. Maybe until Feb 4th,
that would be 2 weeks.
I haven't seen anybody actually using the models nor do I use them myself.
/Markus
On Thursday, Jan
Felt free, thanks for answering.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroup
Please see https://code.djangoproject.com/ticket/25731 for some discussion.
Feel free to offer a patch so we can assess if it's feasible.
On Sunday, January 24, 2016 at 2:57:04 PM UTC-5, is_null wrote:
>
> Hi all,
>
> In Select widgets, as well as many other (including MultipleHiddenInput,
> whe
Hi all,
In Select widgets, as well as many other (including MultipleHiddenInput,
where it's not used) rendering methods all have a choices=() kwarg and use
a chain(self.choices, choices) when rendering.
Maybe I'm missing something, but it seems like this has just been sitting
there since 2006 and
