Ow thanx all but the same component is not always have the same stuff_code. So I prefer stuff_code on Table pc_component :D Anyway thanx for the alternative solution :D Regards, Christine -----Original Message----- From: Renzo Clavijo [mailto:renzo.clavijo@xxxxxxxxx] Sent: Friday, March 23, 2007 23:07 To: OKi98 Cc: php-db@xxxxxxxxxxxxx Subject: Re: PC Inventory System Hi ... I would modify solution 3: Table user user_id First_name last_name Table pc pc_id user_id (FK) Table component component_id component_type (enum) stuff_code desc Table pc_component pc_id (fk) component_id (fk) On 3/23/07, OKi98 <oki98@xxxxxxxxxx> wrote: > > christine wrote: > > > Hi all, > > I need some help to decide the best db design for PC Inventory System. > > There are 2 solution that I thought, you can see it at the attachment. > > Which is the best solution ? Is there another solution ? > > Regards & Thanks, > > Christine > > > Solution 3: > > Table pc > pc_id > > Table component > component_id > component_type (enum) > stuff_code > desc > > Table pc_component > pc_id (fk) > component_id (fk) > > OKi98 > > -- > PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: > http://www.php.net/unsub.php > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php