Chris Jones wrote:
> So, you are storing various types of information on each recipe, such
> as the recipe's name, the directions on how to make it, but then you
> have an ingredients list, which would essentially have to be a 2D
> array. It would store the # of units, the unit type, and what exactly
> the ingredient is...times however many ingredients that particular
> recipe would have. That's where a bigger part of the problem comes
> in, that each recipe could have 3 ingredients, or 20.
This is an ideal situation for a set of linked lists, however, I'm not
familiar enough with DB design to know if that concept translates well
into DBs.
http://en.wikipedia.org/wiki/Linked_list
J
___________________
Nolug mailing list
nolug@nolug.org
Received on 07/14/09
This archive was generated by hypermail 2.2.0 : 08/06/09 EDT