Remove query skip/limit/count constraints documentation #464
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
addisonElliott
changed the title
flovilmart
approved these changes
Aug 15, 2017
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the old Parse hosted backend, there was a maximum query limit of 1,000 objects, skip limit of 10,000, a maximum rate limit of 160 requests / minute, and a count limit of 1,000 objects.
The Parse Server removed all of those constraints but the documentation was never updated to reflect that. Remove all occurrences of these limits in the documentation
See:
#461
parse-community/parse-server#25
parse-community/parse-server#917
parse-community/parse-server#548
parse-community/parse-server#4088