On Tuesday, November 18, 2014 1:58:00 PM UTC+1, Rick van Hattem wrote: > > Hi guys, > > As it is right now Django has the tendency to kill either your browser (if > you're lucky) or the entire application server when confronted with a large > database. For example, the admin always does counts for pagination and a > count over a table with many rows (say, in the order of 100M) can really > stall your app and database servers. >
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.show_full_result_count seems to go in your direction, at least. count(*) performance is implementation-specific, so once again, no one-size-fits-all. Maybe the documentation could be completed, here and there. Claude -- 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...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5c3ffd8f-7ac6-4ac9-863d-875581c3c127%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
