Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
When I do .limit(0) I end up getting the entire dataset back. 0.6.* did not have this behaviour
The text was updated successfully, but these errors were encountered:
Duplicate of #585. This is already fixed in the repo but yet not published to npm.
Just out of curiosity, why do you want to execute limit(0) query?
We have an API that takes count and offset as query parameters. Our users and apps that consume this api have corner cases where they pass in count=0 and expect to get an empty array not the full data set.
When do you think #585 will be published to npm?
Ah sorry abt. that... I'll do a quick pass through and try and get a release out today
Successfully merging a pull request may close this issue.