bugmaster — Sun, 29 Jan 2006 05:59:50 +0000

cross link tables, in other words, one table just consists of the "categories"
the category holds the info to fill in, such as MID, NAME

e.g.
1 Breakfast
2 Lunch
3 Dinner
4 Desserts

MID would be a primary key to that category
then you would fill in all items into the main table, and include a field for the KEY
which would then assossciate that item

say ID, cupcakes, Item Cost, MID
insert '', 'cupcakes' '5.99', '4'

You can then query all MID 4 and it will display Name "Desserts"
and all items in desserts tagged by being MID 4

// get those deserts, im hungry
select table.ID,table.ItemCost, menutable.MID, menutable.NAME from table,menutable where table.MID = '4'

echo those desserts...

1 $5.99 4 cupcakes

above is not perfect but you should get the idea

robbluther — Wed, 25 Jan 2006 16:57:39 +0000

Tim, that is kinda the way I was leaning, all the DB is for is so that the owner can update the menu on the web page by himself... He has daily specials and things like that...

timjpriebe — Wed, 25 Jan 2006 16:55:36 +0000

I would absolutely just do an identifier field. Then, you can handle everything within the SQL statement itself.

Greg K — Wed, 25 Jan 2006 16:55:10 +0000

I fell it wwould really depend on the size of th menu, if you have say only 5-10 items of most categories, then I would use just one table with a colum to indicate category.

Also would depend what the database is for, ie. For customers to place orders, for the management to pick and choose what menu items area available on a given day?

-Greg