What variant of storing liked announcements to choose? Suggest ur own variant too!
- 0
- Android
- Self Hosted
- Users
hi, can you give me some advice about my current project. I have two collections, the first stores all announcements(several attributes(name, price, id...)), the second(own for each person) needs to store liked announcements(with several attributes(name, price, id...)) or only ids of liked announcements. Which variant is better to get list of announcements(with pagination) =>1) bring ids of liked announcements and specify every from the first collection or 2) to to store already liked announcements in the second collection(we will have same attributes in 2 different collections)? Is it significantly longer for user to wait for all requests from server like in 1st variant?
hey, thank you for shifting it here!
I would do a third collection, "liked announcements". It would hold the user id and ad id. I would use pagination. Storing the ids is a good way. In the next versions (https://github.com/appwrite/appwrite/discussions/5179) we will have a type of foreign key, in a single query you can bring all the data
Recommended threads
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....
- User ID case sensitivity
I see that through REST (and SDK as well), getting a user is not case sensitive. And even though documentation does not clearly state that it is, the wording "V...
- Any way to temporarily bypass the email ...
Hey guys, any way to bypass the email verification to use the accounts again? i need to recover some projects that due to recent changes have been stopped, and ...