Back

[SOLVED] Need help in understanding Appwrite DB structures for making ERD

  • 0
  • Databases
  • Web
  • Cloud
Nimit Savant
4 Jun, 2023, 09:56

Exactly, and ERD is really abstract to what database you're using. So yeah just jot down down how you wanna structure your database.

TL;DR
The user needed help understanding the Appwrite DB structures for creating an ERD (Entity Relationship Diagram). They specifically asked about the use case and differences between 'key' and 'fulltext' indexes. The conversation also touched on treating the Appwrite Auth service as a separate database when creating the ERD. The solution provided was to jot down the collections and attributes related to the app and connect them with the users (treating Auth as a separate database). The users also discussed the purpose of Appwrite's internal collections and how they may need to create separate collections to show certain data or protect sensitive information. Overall, the users emphasized that the
safwan
4 Jun, 2023, 10:00

Was going to say this.

An ERD is pretty much like writing pseudo-code. You use pseudo-code to explain in easy terms what a program does. Likewise, you should make your ERD based on your specifics.

I don't see why you would want to know Appwrite's internal DB design for an ERD of your app.

D5
4 Jun, 2023, 10:12

Yes, that's what I'm saying

D5
4 Jun, 2023, 10:19

What's true is that in some cases, Appwrite internal collections/tables ends being a duplication of your collections. For example, users collection (from Auth service): you can't expose it so if you make a blog-like app, you will need to create a separate collection with the database service in order to show the name of the post creator. Same with teams API, but just the opposite: some cases you don't want to expose the email to all users in a team, so to prevent that, you need to use teams only for permissions and then creating another different table/collection to associate teams

Susmita
4 Jun, 2023, 14:16

So, as per your point, I should jot down the collections and the attributes related to it and then connect them with the users(treating Auth as db)

Susmita
4 Jun, 2023, 14:16

Am I right?

Susmita
4 Jun, 2023, 14:16

P. S. First time going to make an ERD

Susmita
4 Jun, 2023, 14:18

So, as per your point, I should jot down the collections and the attributes related to it and then connect them with the users(treating Auth as db)

Susmita
4 Jun, 2023, 14:18

Am I right?

Susmita
4 Jun, 2023, 14:18

P.S. Making ERD for the first time

Nimit Savant
4 Jun, 2023, 14:21

yeah simple :)

Susmita
4 Jun, 2023, 14:23

If you don't mind checking it after it's done, it would be a great help!

Nimit Savant
4 Jun, 2023, 14:23

mostly with yes you can treat auth as db. But when you're creating ERD on basis of that you've to make a copy collection of your Auth service. So as to provide any other attributes you wanna store about your auth users. Like Auth user likes color green, his/her age is 18

Nimit Savant
4 Jun, 2023, 14:27

sure just drop ERD in my dm or in general channel here.

Susmita
4 Jun, 2023, 14:27
Nimit Savant
4 Jun, 2023, 14:30

sure just drop ERD in my dm or in general channel here.

Susmita
4 Jun, 2023, 16:27

Hey @Nimit Savant Check it out

Susmita
4 Jun, 2023, 16:28
Nimit Savant
4 Jun, 2023, 17:45

can you briefly explain what is your database schema about. And I think we should hop out of this channel cause it is for appwrite questions.

Susmita
4 Jun, 2023, 17:53

Yes, I can show you

Susmita
4 Jun, 2023, 17:55

Shall I take ss and paste it here?

Susmita
5 Jun, 2023, 14:56

Hey @Steven Need to know about the use case of key and fulltext indexes and also their differences

Drake
5 Jun, 2023, 14:57
Susmita
5 Jun, 2023, 18:17

Okay, thanks

Susmita
5 Jun, 2023, 18:17

[SOLVED] Need help in understanding Appwrite DB structures for making ERD

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more