Closes#3990.
Closes#3444.

Not that this also removes a now defunct test, that it would return empty results. (Which didn't cover the DivideByZero that it also causes elsewhere.)

Thanks to@mitar and@nhorelik for the input on this! 😄

Hm, but with this change it is not possible to ask for maximum allowed number of requests? Client has to know how much is that.

I don't think0==max is particularly intuitive behavior. If someone wants that, then sure override the class and use your own desired behavior. Treating0 the same as any other invalid value seems a pretty reasonable default.

Hm, but with this change it is not possible to ask for maximum allowed number of requests?

There's a note in the docs about how you might go about doing this.

http://www.django-rest-framework.org/api-guide/pagination/#drf-extensions

TheDRF-extensions package includes aPaginateByMaxMixin mixin class that allows your API clients to specify?page_size=max to obtain the maximum allowed page size.

Hm, what is difference betweenmax_limit andmax_page_size?

So it seems that that extension works only when you have pagination, not when you have offset/limit approach. But maybe a similar mixin can be make for offset/limit as well.

Unfortunately this prevents my frontend client to get the count of a particular resource. What I've been doing is sending aGET request to/resource?limit=0 to fetch the total amount of existing records.

Is there any other good way of doing that?

This breaks old behavior. Clients may have been using ?limit=0 to count objects. Is there any benefit of treating zero as invalid input?

...old behaviour...

That's quite old 😀 v3.4 was mid-2016.

A work around would be to subclassLimitOffsetPagination to check for0 inget_limit before callingsuper.

Thanks. I am doing a similar workaround.

How did you guys fix this?
I upgrade from 3.3 to 3.8, but frontend use &limit=0 not working.