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

List:       php-db
Subject:    Re: [PHP-DB] help in database design
From:       "bedul" <landavia81 () gmail ! com>
Date:       2007-03-29 1:35:04
Message-ID: 003801c771a2$81caa310$e40b1e0a () mis01
[Download RAW message or body]

NOT QUITE..ups.. my bad
----- Original Message ----- 
From: "Chris" <dmagick@gmail.com>
To: "Suprie" <suprie1983@gmail.com>
Cc: <php-db@lists.php.net>
Sent: Thursday, March 29, 2007 6:53 AM
Subject: Re: [PHP-DB] help in database design


> Suprie wrote:
> > hi all,
> > 
> > i need help in design a database, our office is hospital equipment 
> > supplier,
> > we had a list of items, each items had it's own configuration, and
> > each item could consist of several item. we also had contract that
> > have a lot of site, sometimes equipmend that have been ordered
> > different from what the site received, in that case we made a change
> > request...
> > 
> > for now we have this
> > 
> > |contract|------|has|-----|site|
> >                       |
> >                       |
> >                   |item|----|material|
> >                       |
> >                       |
> >              |configuration|
> > 
> > but i really confused about the Change Request thing, we have to keep
> > both what have been ordered and what have been received... where
> > should i put it, sorri for my bad english
> 
> Why does that have to fit into this scheme?
> 
> Why can't it be separate?
well as u mention above.. he already seperated while ago.. 
item and material was 2 different table. and yet it should seperated..

i alreadt received the newest.. i hope he posted but  i posted again
==================================================
site is, the items destination , owh i forgot beside the goods we also
provide services, that could change also just like other items depends
the situation.
=====================================================

as i write above.. he mistaken on what the flow goes

> 
> create table change_requests (
>    request_id primary key .. blah blah,
>    item_ordered text,
>    item_order_date timestamp, // so you know when you ordered it
>    item_received text,
>    item_receive_date timestamp // so you know when you received it.
> );
> 
> problem solved ?


> 
> -- 
> Postgresql & php tutorials
> http://www.designmagick.com/
> 
> -- 
> 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]