Re: Database Design Advice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux