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.
In the past I've simply patched Django to include a few "security" features for cases like these so someone can't accidently kill the site by doing something silly, but I was wondering if it would be a good idea to include some of these configurable options in the core. Examples: - If COUNT_LIMIT is set than wrap counts in a subquery and limit the results: SELECT COUNT(*) FROM (SELECT pk FROM table LIMIT <COUNT_LIMIT>) - When someone does "if queryset" automatically limit it to a default slice size so someone doesn't accidently fetch all rows in the queryset. ~wolph -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a430471d-2879-4b16-8308-c50dda985977%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
