Closed jablkoj closed 3 years ago
not qs can be very slow for large querysets.
not qs
I tested calling prev_in_order(sample, qs=Sample.objects.all()) with 16000 Samples and it took 200-500ms while the rest of next_or_prev_in_order function took less than 10ms. (Django==3.0.6; django-next-prev==1.0.1)
prev_in_order(sample, qs=Sample.objects.all())
next_or_prev_in_order
Huh, thanks for this, so is not qs actually evaluating the queryset?
not qs
can be very slow for large querysets.I tested calling
prev_in_order(sample, qs=Sample.objects.all())
with 16000 Samples and it took 200-500ms while the rest ofnext_or_prev_in_order
function took less than 10ms. (Django==3.0.6; django-next-prev==1.0.1)