ultimately, there are tradeoffs and it's up to you.
you can research database normalization, but in practice, databases aren't always normalized because it depends on the use case
[SOLVED] Scalable database design
@loup no need to delete your posts. it can be helpful for others to see
Sry I’ve miss clicked… idk how to undo
i don't think you can undo a delete. no worries
I'm interested in your final decision
Well I dont have the final decision because I dont have enought experience in dev
But my actual setup is one collection per functionnality
But its so hard to maintain consistency between each document
There is an exemple about my database design but isnt really good
Maybe I can create another table movie_actions which is a collection connected to movie_liked, movie_review, movie_rated, movie_watched, movie_watchlisted, movie_guidelisted. Like this I can only call the movie_actions to get all action from user about a movie
But that make a lot of collection
Recommended threads
- Google Auth not working in a React App
Authentication with Google has failed. It redirects back to the signin route in React. Attached screenshots for configuration of Google console and Appwrite Go...
- Bug Report: Crash when trying to createR...
https://github.com/appwrite/sdk-for-android/issues/96 I think the bug is related with this one https://discord.com/channels/564160730845151244/1443887021314539...
- Dokploy docker compose
Hey guys hope y'all doing well, I was wondering if anyone could share a working 1.8.0 docker-compose that works with Dokploy I tried making it but it just does...