You're right.
I have already posted a 3 tables solution: recipes, ingredients and
recipeingredients.
Adolfo
On Sun, 2002-12-22 at 14:10, Jeff Snoxell wrote:
> > > I'm designing a delivery program with php and mysql, and I'm
> > > having troubles with some tables, my problem is with the
> > > rec
> I'm designing a delivery program with php and mysql, and I'm
> having troubles with some tables, my problem is with the
> recipes, the recipes are divided into two tables one with a
> recipe id and description the other detailing the
> ingredients, of each particular recipe, that's where my
> p
> -Original Message-
> From: Ricardo Fitzgerald [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, December 22, 2002 11:22 AM
> To: [EMAIL PROTECTED]
> Subject: Help with database Design
>
>
create table recipes(
rid int not null primary key,
rname ) ;
create table ingredient(
iid int not
Ricardo, you're asking how to normalise your database. There are links to
some good intro tutorials at http://www.artfulsoftware.com/dbresources.html
PB
-
[filter fodder: sql, mysql]
> Hi,
>
> I'm having problems trying to figure which is the best way to solve a
design
> :
>
> I'm designing
Ricardo, you're asking how to normalise your database. There are links to
some good intro tutorials at http://www.artfulsoftware.com/dbresources.html
PB
-
> Hi,
>
> I'm having problems trying to figure which is the best way to solve a
design
> :
>
> I'm designing a delivery program with php
