t attributes.description
> From attributes_links
> On attributes_links.attribute_id = attributes.id
> Where attributes_links.dvd_id = 1
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 08, 2006 5:41 AM
>
rom attributes_links
On attributes_links.attribute_id = attributes.id
Where attributes_links.dvd_id = 1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 5:41 AM
To: Scott Haneda
Cc: MySql
Subject: Re: Best way to design one to many quer
> Been wondering this for a while now, I can explain how I do it, but
> I am sure there are better ways.
> ...
Maybe I'm really missing something here but I think that your querying
problem arises from bad data design. This is what I'd do:
Product table:
ProductID
some other stuff
for instance to count how many with such attribute),
the query will fly.
The link table also allows one to many relationships.
Believe me, that's the way to do it.
-Original Message-
From: Scott Haneda [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 07, 2006 10:45 PM
To: MySql
Been wondering this for a while now, I can explain how I do it, but I am
sure there are better ways.
I have products and attributes, for example:
Product A
nice
sweet
fast
funny
Attributes are arbitrary, attributes are in a separate table. Yes, I could
add fields for the attribut
