-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
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? Sign in to your account
🐛 Bug Report: Increase Pagination maximum offset from 5000 #5506
Comments
…0 for list documents pagination appwrite#5006 fixed with adding APP_LIMIT_DOCUMENT_COUNT new variable added in init.php with value as 1000000
Raised PR - #5508 Please review it! & lemme know if any change is required! |
Hi, there is a reason for this. |
In case you have a need to remove this limit in a self-hosted Appwrite, you can do so by overriding
appwrite:
image: appwrite/appwrite:1.3.7
container_name: appwrite
<<: *x-logging
restart: unless-stopped
networks:
- appwrite
labels:
...
volumes:
...
- /root/customized/init.php:/usr/src/code/src/app/init.php
depends_on:
...
environment:
...
const APP_LIMIT_COUNT = 5000000; Then you're set to go. |
Also, this ☝️PR can give any self-hoster of Appwrite the option to change this option in the |
That will be quite usefull for my project. I need to fetch all documents in appwrite function once a day but that limit force me to make multiple requests for that |
👟 Reproduction steps
Pagination: The maximum offset is 5000. But in some cases, i want use offset > 5000 . I want have default max offset = 5000 and i can config max offset from ENV.
👍 Expected behavior
Pagination: The maximum offset is 5000. But in some cases, i want use offset > 5000 . I want have default max offset = 5000 and i can config max offset from ENV.
👎 Actual Behavior
Pagination: The maximum offset is 5000. But in some cases, i want use offset > 5000 . I want have default max offset = 5000 and i can config max offset from ENV.
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: