I'm confused about the structure of Databases.
We have Database -> Collection -> Document -> Attributes
. This somehow seems to be one layer too much.
I want documents that contain additional information about users, e.g. how many products they bought, favourite product, ...
How should I structure my Database? I thought of
[Database] UserInfo -> [Collection] ??? -> [Document] User1 -> [Attributes] all attributes of this user
.
What should "collection" be? Or do I have a fundamental misunderstanding of how databases are supposed to be structured?
Recommended threads
- Concurrency issue?
I have this server side code (.NET SDK): ``` //no label is set, but also no exception is thrown Task<User> updateLabelTask = users.UpdateLabels(studentId, ne...
- Using queries on partial date
Hello, I need to get documents from Database that start with "2024-11" but it's not returning anything. Here current used for this query `export async functio...
- Quick Question
I installed appwrite on my local machine. Build my app. But now I don't have any idea how to deploy it on my vps hosting along with that databases storage funct...