On Mon, Nov 24, 2014 at 3:32 PM, Christophe Pettus <x...@thebuild.com> wrote:
> In your particular case, where you have the relatively unusual situation > that: > > 1. You have this problem, and, > 2. You can't fix the code to solve this problem. > > ... you probably have the right answer is having a local patch for Django. > Alternatively, the same could be accomplished with a custom database backend that enforces whatever limit value is desired. If I needed this behavior, I'd probably tweak the query.low_mark and query.high_mark values in SQLCompiler.as_sql before passing it along to the parent. I think it's safe to say that this functionality is unlikely to find its way in to Django, but if you have questions about the custom database backend approach, feel free to contact me. Regards, Michael Manfre -- 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/CAGdCwBu1FY_f34vno33WD6npFoRNokmgYwO8G2dy1U%3DUsfd2hw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
