Thanks, folks. I appreciate the pointers. This just goes to show that extensive knowledge of relational theory can have little effect on real-life projects. Edward Dudlik Becoming Digital www.becomingdigital.com ----- Original Message ----- From: "mike karthauser" <mikek@brightstorm.co.uk> To: "Becoming Digital" <subs@becomingdigital.com>; <php-db@lists.php.net> Sent: Tuesday, 13 May, 2003 14:03 Subject: Re: Database Design Advice on 13/5/03 6:40 pm, Becoming Digital at subs@becomingdigital.com wrote: > I'm setting up a database for a new project and I keep wavering on one aspect > of > the design. The end result is to be a searchable menu for a restaurant's > website and I cannot decide if it is best to simply use one table for all menu > items (food) or use tables for each category (pasta, appetizers, etc). I > currently > have a table listing said categories (categories) but I simply can't decide > which > is better for this application. Thank you all for your advice. http://www.databasejournal.com/sqletc/article.php/26861_1474411_1 It should be very obvious what structure you need once reading this.. -- Mike Karthauser Managing Director - Brightstorm Ltd Email >> mikek@brightstorm.co.uk Web >> http://www.brightstorm.co.uk Tel >> 0117 9426653 (office) 07939 252144 (mobile) Snailmail >> Unit 8, 14 King Square, Bristol BS2 8JJ -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
