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
- Site deployment keeps getting failed
Hi good folks, need a hand with Sites deploy Error on every deploy: Synchronous function execution timed out... duration doesn't exceed 30 seconds [exact log ...
- Relation Question
How do I create a relation from table y to an others x.$id. in my example I have a users table where I use Appwrites unique User IDs and I want other tables fo...
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...