[SOLVED] DATABASE MODEL (STRUCTURE)

ookay

TL;DR

User is discussing database structure and asking for guidance on how to update user balance without creating a new document. There is a reference to an outdated version of Appwrite in the cloud. Another user suggests using relationships and a user ID field. The original user expresses gratitude and mentions using self-hosted Appwrite in the future. There is a question about how to match a user to its various documents. The user updates the thread with an updated diagram. The conversation ends with a question about the beta end date. Solution: User is provided guidance on using relationships and a user ID field to match a user to its documents. The user expresses intent

will beta end this month? I will be done by then

Not sure, they said by the end of ths year

Updated diagram

Ouch

I appreciate you dearly

I didn't do anything to deserve this

hi @D5 thanks for the other day

but how do I match a user to all it's various documents?

Are you using cloud or self-hosted?

currently using cloud @D5

but will use self-hosted when am pushing to production

In cloud, you should manage relationships manually

Basically you create a userID field and you put there the user ID

I just did local installation and found relationships

I appreciate you @D5

Perfect

[SOLVED] DATABASE MODEL (STRUCTURE)

that means appwrite cloud is not up to date?

besides, @D5 how do I store user balance in a way that after a transaction is successful, instead of having a new document which is not needed, it will update existing one?

Nope, cloud is using 1.1.2 and current appwrite version in 1.3.7

okay then

You should modify it with a function, when a new transaction is made

ok, thanks

Also when for creating a transaction you should have a function so you could update the value with the same function

ok then, thanks

Reply to this thread by joining our Discord

Reply on Discord