Hi Rick,
On Sunday 23 November 2014 14:11:13 Rick van Hattem wrote:
>
> So please, can anyone give a good argument as to why any sane person would
> have a problem with a huge default limit which will kill the performance of
> your site anyhow but isn't enough to kill the entire system?
>
...because Django is also used to implement batch processes, and you'd be very
surprised if your system, which works well enough for a year or so, suddenly
has its night-jobs starting to fail one day because some size-limit has been
reached.
The Django project has traditionally held the position, with regard to such
proposals, that we should avoid making such decisions for our users, but we
should allow them to make them by themselves; this can also lead to more
general solutions.
In this case, I think you could get support for allowing yourself query-
validation hooks -- say, allow installing a function that will be called by
the ORM when query results are received, before turning them into objects. I
think this lets you solve your problem outside of core (and then, if your
solution proves useful and popular, it may go into core as well). This could
also allow other interesting functionalities, I suspect, if it is allowed to
modify (and not just validate) the results.
I think (speaking only for myself, of course) that a proposal along these
lines has a better chance of gaining traction.
HTH,
Shai.
