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
- Dynamic Roles
I tried to store a row with this permissions: permissions.push( Permission.read(Role.users("verified")), Permission.write(Role.label(`c-${calend...
 - appwrite auth problem regarding the sess...
Hi, I have problem with auth. When I try to login/signup using OTP, at the end session.secret is empty, i have searched online and in the docs but i cannot find...
 - log out failure
I am trying to set up the user sign up/log in/log out and while I have got the sign up/log in to work, log out keeps failing. i am keeping it simple with only r...