|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hello,
I've been designing a schema for a web app that will allow users to create a weekly meal plan and shopping list. At the heart of the design is the model for recipe data. I currently have a hierarchy of: Menu eg. Mozzarella Salad, Beef Casserole , Apple Flan w. Raspberry cream. Meal eg. Apple Flan w. raspberry cream Dish eg Apple Flan Recipe - eg pastry case, apple sauce, topping Ingredient - eg flour At the lowest level - ingredient, I also have: Measurement Method Equipment tables My question is, how do I connect these tables? I've created an 'ingredient list' table, which links the ingredient, measurement and recipe tables and contains: recipe ID Quantity Measurement ID Ingredient ID Do I need to create list tables to link every other set of tables up the hierarchy? How do other systems deal with hierarchies? Can you ? Thanks you for your . Hugo |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
On 19 Oct, 13:54, h...@laterooms.com wrote:
> Hello, > > I've been designing a schema for a web app that will allow users to > create a weekly meal plan and shopping list. > > At the heart of the design is the model for recipe data. > > I currently have a hierarchy of: > > Menu eg. Mozzarella Salad, Beef Casserole , Apple Flan w. Raspberry > cream. > Meal eg. Apple Flan w. raspberry cream > Dish eg Apple Flan > Recipe - eg pastry case, apple sauce, topping > Ingredient - eg flour > > At the lowest level - ingredient, I also have: > > Measurement > Method > Equipment tables > > My question is, how do I connect these tables? I've created an > 'ingredient list' table, which links the ingredient, measurement and > recipe tables and contains: > recipe ID > Quantity > Measurement ID > Ingredient ID > > Do I need to create list tables to link every other set of tables up > the hierarchy? > How do other systems deal with hierarchies? > Can you ? > > Thanks you for your . > > Hugo http://del.icio.us/Captain_Paralytic/hierarchical |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
On Oct 19, 2:01 pm, Captain Paralytic <paul_laut...@yahoo.com> wrote:
> On 19 Oct, 13:54, h...@laterooms.com wrote: > > > > > Hello, > > > I've been designing a schema for a web app that will allow users to > > create a weekly meal plan and shopping list. > > > At the heart of the design is the model for recipe data. > > > I currently have a hierarchy of: > > > Menu eg. Mozzarella Salad, Beef Casserole , Apple Flan w. Raspberry > > cream. > > Meal eg. Apple Flan w. raspberry cream > > Dish eg Apple Flan > > Recipe - eg pastry case, apple sauce, topping > > Ingredient - eg flour > > > At the lowest level - ingredient, I also have: > > > Measurement > > Method > > Equipment tables > > > My question is, how do I connect these tables? I've created an > > 'ingredient list' table, which links the ingredient, measurement and > > recipe tables and contains: > > recipe ID > > Quantity > > Measurement ID > > Ingredient ID > > > Do I need to create list tables to link every other set of tables up > > the hierarchy? > > How do other systems deal with hierarchies? > > Can you ? > > > Thanks you for your . > > > Hugo > > http://del.icio.us/Captain_Paralytic/hierarchical Thank you for that, it's really interesting, and is making me question whether what I'm trying to do is actually to create a hierarchy... I think that the hierarchies I will be creating will be so varied they would almost be considered dynamic. For example I can have a menu of meal 1, meal 2, meal 3. and another menu of meal 4, meal 5, meal 6. but we can also have a menu of meal 1, meal 4 and meal 3. So should I be looking at relating the tables rather than looking at storing the information hierarchically? Thanks again for your . Cheers, Hugo |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
== Quote from hugo ( hugo@laterooms.com)'s article
> On Oct 19, 2:01 pm, Captain Paralytic <paul_laut...@yahoo.com> wrote: > > On 19 Oct, 13:54, h...@laterooms.com wrote: > > > > > > > > > Hello, > > > > > I've been designing a schema for a web app that will allow users to > > > create a weekly meal plan and shopping list. > > > > > At the heart of the design is the model for recipe data. > > > > > I currently have a hierarchy of: > > > > > Menu eg. Mozzarella Salad, Beef Casserole , Apple Flan w. Raspberry > > > cream. > > > Meal eg. Apple Flan w. raspberry cream > > > Dish eg Apple Flan > > > Recipe - eg pastry case, apple sauce, topping > > > Ingredient - eg flour > > > > > At the lowest level - ingredient, I also have: > > > > > Measurement > > > Method > > > Equipment tables > > > > > My question is, how do I connect these tables? I've created an > > > 'ingredient list' table, which links the ingredient, measurement and > > > recipe tables and contains: > > > recipe ID > > > Quantity > > > Measurement ID > > > Ingredient ID > > > > > Do I need to create list tables to link every other set of tables up > > > the hierarchy? > > > How do other systems deal with hierarchies? > > > Can you ? > > > > > Thanks you for your . > > > > > Hugo > > > > http://del.icio.us/Captain_Paralytic/hierarchical > Thank you for that, it's really interesting, and is making me question > whether what I'm trying to do is actually to create a hierarchy... > I think that the hierarchies I will be creating will be so varied they > would almost be considered dynamic. > For example > I can have a menu of meal 1, meal 2, meal 3. and another menu of meal > 4, meal 5, meal 6. but we can also have a menu of meal 1, meal 4 and > meal 3. > So should I be looking at relating the tables rather than looking at > storing the information hierarchically? > Thanks again for your . > Cheers, > Hugo sounds like you need to be looking at relating the tables. if you do this right, then you'd be able to create meals dynamically and you wouldn't be limited to any structures. -- POST BY: lark with PHP News Reader ;o) |
|
![]() |
| Outils de la discussion | |
|
|