From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
---|---|
To: | operationsengineer1(at)yahoo(dot)com, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Data (Table) Structure Question |
Date: | 2006-11-24 17:40:06 |
Message-ID: | 762628.4419.qm@web31806.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
> i have contacts, customers and employees that i want
> to manage in a db application.
> i can think of two ways to do this.
> first, have a table for each and fill each with all
> the relevant data:
> 1. t_custoemrs
> 2. t_employees
> 3. t_contacts
> second, have a contacts table that records data that
> is repeated throughout each table (ie, name, address,
> phone, etc...)
> i could then have a t_employees table with a foreign
> key to the t_contacts table id. this table would only
> have employee related information and would link back
> to contacts.
> t_customers would do the same - list only customer
> specific information.
> i think the latter way is the way to go, but i'm not
> sure. i don't particularly like t_contacts as the
> name of the general table. maybe i need to name it
> persons.
> anyway, i'd value the input of some more experienced
> developers.
Are you trying to find a way to relate an employee to one or more customers?
Regards,
Richard Broersma Jr.
From | Date | Subject | |
---|---|---|---|
Next Message | operationsengineer1 | 2006-11-24 19:51:30 | Re: Data (Table) Structure Question |
Previous Message | Tom Allison | 2006-11-24 16:42:34 | Re: Triggers and Functions |