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
- Rate límit reset
I've made an error in the code by not setting a limit on how much rows should i get per request because i was working with a small db for testing. Last night Iv...
- How to set permissions using the createO...
Hi, I'm trying to create a set of registers in a table using the tableDB.createOperations function, but it seems like it doesnt support/expect the usage of the ...
- Fulltext index creation fails due to Inn...
I'm running a self-hosted Appwrite 1.8.1 instance and encountering an issue when creating fulltext indexes on a collection. **The Problem:** Fulltext index cre...