Re: Adv. Mysql query

2003-08-04 Thread terrence brannon
- Original Message - From: "Andy Jackman" <[EMAIL PROTECTED]> To: "Mattias Larsson" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, August 02, 2003 4:23 PM Subject: Re: Adv. Mysql query > Mattias, > It may not be such a go

Re: Adv. Mysql query

2003-08-03 Thread Andy Jackman
Mattias, Your 'blueprint' table looks good. > This where "itemID" corresponds to a item in the master table and the > "componentID" ALSO referes to items in the Master table??? Correct. This allows 'recursive' components. For example, Item 3 contains components 1,3,4 and component 4 is actually

Re: Adv. Mysql query

2003-08-02 Thread Andy Jackman
Mattias, It may not be such a good idea to store the 6 items in 1 record. An alternative structure is one table with Item ID and Name and another with Item Id and Component Id, both of which point back to item id in the first table. This avoids having to know how many components there are and allow

Adv. Mysql query

2003-08-02 Thread Mattias Larsson
Hi there. I have a little problem with a sql-query I'm trying to get together. Well I got it to work halfways. I have a table with items, which are composed of 1-6 other items, which is saved in the same table. You might call it a recursive query, I need to get the names of the components tha