-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
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 |
@FotieMConstant it could work well. |
We could collect our data and have a separate database also |
But not the same data that we store in firebase it would be redundant, |
Yeah, i think so as well. Please does anyone has Postgre or Mongo db online we can use? |
@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 |
How much does it cost if we want to upgrade! Any idea? |
@FotieMConstant the pricing plan varies greatly, here is a link you can check it out |
Relational Database Structure@FotieMConstant @RonaldColyar before we join anything i'll share the structure of the db here so we could discuss it
NB : I used the information i had in mind on the project and that which @RonaldColyar shared recently to come up with this database |
Assuming we are just going to continue using firebase:
Users
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 :
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
}
The text was updated successfully, but these errors were encountered: