The admin list page performs a count(*) (twice!) when viewing the list page
of a model. One of these counts can be disabled, but the pagination count
can not be. On huge tables, this can be a massive performance
issue. https://code.djangoproject.com/ticket/8408 was created to disable
the count,
Yes we should be documenting edge cases and unexpected results. We have a
page that discusses some issues with server side
cursors:
https://docs.djangoproject.com/en/dev/ref/databases/#transaction-pooling-server-side-cursors
Is there anyway we could make SSC work without a transaction? We'd pre
I've made a ticket for this: https://code.djangoproject.com/ticket/28469
On 7 April 2017 at 11:18, Berker Peksağ wrote:
> On Fri, Apr 7, 2017 at 9:54 AM, Adam Johnson wrote:
> > Personally I'd be in favour of adding such classes. It seems against the
> > batteries-included philosophy that Djang