Geek asks and answers

Database Schema Dilemmas

I am developing a database schema for a recipe database. Do you have any ideas on teaching my existing model? My problem with bigges is the RECIPE_INGREDIENT table. enter image description here

+3
source share
3 answers

In RECIPE_INGREDIENT, you can safely delete RECIPE_INGREDIENT_ID and replace it (INGREDIENT_ID, RECIPE_ID) as a combined primary key, similar to the recipe_tags table. That is, if you do not plan to allow the ingredient to appear twice in the recipe.

Otherwise, the design looks good to me. What do you want to improve? This can help if you explain what you are trying to do with the database and what queries you plan to run.

+1
source

, . , , , . , , INGREDIENT_DESC RECIPE_INGREDIENT , RM_INGREDIENT.

+1

Typically, you will have some kind of process or step that the recipe has many of which have many ingredients.

Recipe 1 - Many Recipe Steps

Recipe Step 1 - Many Recipe Ingredients

+1
source

More articles:


All Articles