My categories table has several 'types'.
2 = size
3 = Country
5 = category description (fashon tshirt, vneck etc)
so I'm having to puick out category AND size so that's why I'm
refering to it twice.
Perhaps I should have had a size table and a description table etc..
but I thought it'd be quicker to keep them all in one table?
quicker? no ;o)
by "generalizing" you have simply made the query appear more complex
i can understand why using a relationship for sizes (rather than having,
say, a varchar(12) column for the size right in the product table), because
this forces users, when entering new products, to select only from a given
set of valid sizes...
... but a table for descriptions is pretty unusual
also, can you see now why i was confused by your use of the aliases "parent"
and "child"? you should at least use alias names like "size" and "country"
and "description"
your query speed will get even better when you take off DISTINCT
rudy
____ � The WDVL Discussion List from WDVL.COM � ____
To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or
use the web interface http://e-newsletters.internet.com/discussionlists.html/
Send Your Posts To: [email protected]
To change subscription settings, add a password or view the web interface:
http://intm-dl.sparklist.com/read/?forum=wdvltalk
________________ http://www.wdvl.com _______________________
You are currently subscribed to wdvltalk as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
