
Hello, I have a userData collection which stores a users info like address etc. I have a couple of relationships with other collections which could have a lot of data related to the user. My question is when i query the userData document for a user I see that I get returned the related collections documents also. My question is how many records will it return, i'm guessing its the rate limit of 25. I'll need to know since one of the related collections is userEvents and will eventually have a decent amount of data. What I do know is instead of querying the userData and separately querying the userEvents I just query the userData and add the userEvents to a list because the data is already there. How will this work with pagination and what order does the related collection data come in? from the last created to the oldest or from the first created to the newest? Is there an option to control this?
Thanks!
final data = await ref.read(databaseProvider).listDocuments(
databaseId: Database.databaseId,
collectionId: Collections.userData,
queries: [
Query.equal('accountId', ref.read(sessionController).currentUser!.$id)
],
);```

Right now, all the related data is returned 😅
We plan to add a way to paginate

I guess no worries for the time being. Thanks!

Relationship and Rate Limit [SOLVED]

[SOLVED] Relationship and Rate Limit
Recommended threads
- ❗[Help] Function stuck in "waiting" stat...
Hi Appwrite team 👋 I'm trying to contribute to Appwrite and followed the official setup instructions from the CONTRIBUTING.md guide to run the platform locall...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
- Database Double Requesting Error.
I am getting error for creating new document in an collection with new ID.unique() then too getting error of existing document. When button is pressed one docum...
