The data structure behind meals, recipes, and ingredients can get pretty complicated.
Youโll want to figure out which data entities should have a one to many or many to many relationship.
I would recommend having a one to many relationship between ingredients and meals, so that one ingredient can be used for many meals. This would mean you would have a meal_id column in your ingredient table that is a ref data type to the meal table. You can also use AppSheetโs โIs a part ofโ feature to add multiple ingredients at once when youโre adding a new meal record:
One drawback with my suggestion is that an ingredient wouldnโt be able to change other attributes like amount or quantity between different meals. Instead, you would have to create multiple ingredients with the same name but different attributes.
User | Count |
---|---|
32 | |
31 | |
30 | |
18 | |
17 |