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
- Bulk API limitations in self-hosted serv...
Environment: Appwrite Selfhost SDK: node-appwrite 28.0 Calling `upsertRows` (also applies to `createRows`/`updateRows`/`deleteRows`) with more than 100 rows fa...
- Self Hosted GitHub connection not adding...
After upgrading to 1.9.6 i noticed that i cannot search for new repositories when trying to add new functions. I removed the existing github connection via Set...
- Android SDK: Kotlin null Value Not Updat...
Hi team, I think you should check the Android SDK implementation once, as it seems to have an issue handling Kotlin **null** values. For example: When I send:...