Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Db structure! #37

Open
RonaldColyar opened this issue Apr 8, 2021 · 11 comments
Open

Db structure! #37

RonaldColyar opened this issue Apr 8, 2021 · 11 comments

Comments

@RonaldColyar
Copy link

RonaldColyar commented Apr 8, 2021

Assuming we are just going to continue using firebase:

Users

  • DisplayName
  • Username
  • DisplayPhoto
  • Groups(priority groups like family , lovers,friends etc) the groups will contain the usernames of the people and its priority. The priority will be normal , above normal , and number 1.
  • Sounds
  • Contacts (a list of usernames)
  • Received sounds (the sounds that others sent to you! This will just be a link to the sound in the other person's storage , but you may think this is an issue because it seem like users can read each other's data. We can solve this issue by making rules that limit users to only reading a specfic portion of the user's data model)
  • Contact Requests.
    when someone sends a contact request it will be placed on both parties user and if the user accepts , it will validate that both users have agreed to become contacts.

I don't want users to be able to write to each other's contacts .

So :

  1. initally the user 1 will log in send the contact request to user 2 ,
  2. once accepted each will become friends/contacts.

so it would look something like this for visualization!!:

user1/requests = {
type: outgoing ,
to: user2,
status: pending
}

user2/requests = {
type: received
from : user1,
status : pending
}

@RonaldColyar
Copy link
Author

@FotieMConstant

@RonaldColyar
Copy link
Author

@quiet-programmer

@FotieMConstant
Copy link
Member

Are we finally sticking to firebase? Because I think we should get something we can have more control on like I talked with @RonaldColyar. Both now and later

@RonaldColyar
Copy link
Author

@FotieMConstant it could work well.

@RonaldColyar
Copy link
Author

We could collect our data and have a separate database also

@RonaldColyar
Copy link
Author

But not the same data that we store in firebase it would be redundant,

@FotieMConstant
Copy link
Member

Yeah, i think so as well. Please does anyone has Postgre or Mongo db online we can use?

@dilanlongla
Copy link
Member

@FotieMConstant we could configure a postgre db on heroku but it will be limited as they grant a max of 20 simultenous connections to the db

@FotieMConstant
Copy link
Member

How much does it cost if we want to upgrade! Any idea?

@dilanlongla
Copy link
Member

@FotieMConstant the pricing plan varies greatly, here is a link you can check it out
postgreSQL db Heroku pricing plan

@dilanlongla
Copy link
Member

Relational Database Structure

@FotieMConstant @RonaldColyar before we join anything i'll share the structure of the db here so we could discuss it

  • Here we have the class diagram of the database

class diagram

  • Here have the Physical datamodel

pdm

NB : I used the information i had in mind on the project and that which @RonaldColyar shared recently to come up with this database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants