What you're looking at is a taxonomy of foods. Modelling each food type however using individual tables is not going to be the answer. What happens when a new food comes along? You insert a row into your foods table, however you now need to add a new table for the new particular food items.
To me it look rather similar to the manager -> employee situation in many businesses. And i know rudy has some good examples of that type of SQL modelling. Just get him to shed some (my brain isn't working properly yet today so I can't remember what that type of modelling is called).