Re: Best way to design one to many queries

2006-03-08 Thread cnelson
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

RE: Best way to design one to many queries

2006-03-08 Thread Nicolas Verhaeghe
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 queries

Re: RE: Best way to design one to many queries

2006-03-08 Thread cnelson
-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 queries Been wondering this for a while now, I can explain how I do it, but I am sure there are better

RE: Best way to design one to many queries

2006-03-07 Thread Nicolas Verhaeghe
Your method is wrong because if you are looking for 5, then 56 will match and also everything that has 5 in it. Unless you include the spaces and look for : '% 5 %' but then you need to add a space at the beginning and at the end of your attributes field. That method is way too cumbersome and