Last Friday I fixed a bug in one of our server side functions where it became clear that not all records where considered because of pagination. I see the value of pagination when sending data to the client via a REST interface (or something like that), but when I query data on the server it feels kinda wired. In this cases I wanted to get all foreign keys from a certain field of that collection. So I needed to recursively cursor over the whole thing. Is there a way to avoid this?
We use Web/ JS on the client and Node.js in the Functions.
Hi, what is the current size you are working with in pagination?
Default, which is 25. But the problem is always there.
If it's the cloud you can change the limit up to 100 and in the latest version up to 5000
To do so send Query.limit(100) with your request.
But it's recommend you use the pagination for performance and overwhelming your sever.
Recommended threads
- HUGE OUTRAGE IN APPWRITE, I CANNOT ACCES...
I have 2k users trying to access, sending me messages. What am I supposed to do? Please solve this asap.
- All my apps are not opening now
All my apps are not opening now 200+ apps are not opening plz fast
- Dotnet functions on cloud
I'm trying to deploy my .Net8 functions to my project on cloud.appwrite through the CLI. I'm getting this error.