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

Recipe: Mock Database #34

Open
DConnorFong opened this issue Oct 19, 2019 · 3 comments
Open

Recipe: Mock Database #34

DConnorFong opened this issue Oct 19, 2019 · 3 comments
Assignees

Comments

@DConnorFong
Copy link
Collaborator

What are the exact tables you are going to need? Please discuss and add a document.

@DConnorFong DConnorFong assigned DConnorFong and no-or and unassigned DConnorFong Oct 19, 2019
@no-or
Copy link
Contributor

no-or commented Oct 25, 2019

Hey,
I am thinking NoSQL (MongoDB) with the following collections. Please, let me know if I need to make any adjustments:

userRecipe

  • user_id
  • recipe_ids []

recipes

  • id
  • name
  • description
  • instructions [{number, description}, {number, description}, ….]
  • ingredients [{id, qty}, {id, qty}, …..]

@DConnorFong
Copy link
Collaborator Author

I think that using an SQL structure is better, but if you prefer NoSQL, we can try to prototype with it.

This is fine, although thinking about scalability, idk if qty will be enough. There are a lot of different ways to express that (units: a number of apples; weight: mg/Kg; volume: ml/L).

@no-or
Copy link
Contributor

no-or commented Oct 25, 2019

I have not done any project (from scratch) in SQL before. I can give it a try if you want.

And yeah, you are right, we might need to modify qty. I will make the adjustments and comment again for your feedback.

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

2 participants