[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-db
Subject:    RE: [PHP-DB] PC Inventory System
From:       "christine" <christine () ibii ! ac ! id>
Date:       2007-03-26 1:38:13
Message-ID: 55.0F.35470.31427064 () pb1 ! pair ! com
[Download RAW message or body]

 
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@gmail.com] 
Sent: Friday, March 23, 2007 23:07
To: OKi98
Cc: php-db@lists.php.net
Subject: Re: [PHP-DB] 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@centrum.cz> 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

[prev in list] [next in list] [prev in thread] [next in thread]