From: Aaron Bono <postgresql@aranya.com>
To: D'Arcy J.M. Cain <darcy@druid.net>
Cc: Curtis Scheer <Curtis@daycos.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Table relationships
Date: Tue, 9 Jan 2007 09:13:35 -0600
Message-ID: <bf05e51c0701090713v1564455esc175cf3bb402393c@mail.gmail.com> (raw)
In-Reply-To: <20070109094113.064bae02.darcy@druid.net>
References: <031936836C46D611BB1B00508BE7345D04DC1BB5@gatekeeper.daycos.com>
<20070109094113.064bae02.darcy@druid.net>
On 1/9/07, D'Arcy J.M. Cain <darcy@druid.net> wrote:
>
> On Mon, 8 Jan 2007 17:07:56 -0600
> Curtis Scheer <Curtis@DAYCOS.com> wrote:
> > -> Is there a difference between an address for the customer detail and
> an
> > address for the customer?
> >
> > Not really an address is an address, it's a matter of specify an address
> for
> > the customer master record which basically represents an entire customer
> > while the customerdetail represents departments within that company that
> > might be at a different address then the company's main office for
> instance.
>
> Could be that you need another table. Sounds like you have something
> like;
>
> company <===> address <===> detail
This approach implies that the address defines the relationship between a
company and the detail (the other departments/offices). I cannot think of a
business model that would use this though there probably are some...
Another alternative is to add another table which just holds the
> address:
>
> company <===> department <===> detail
> ^ ^
> | |
> \==> address <==/
I'm not sure what this relationship is for. It would appear that a
department can have different addresses for different companies.
There are many possibilities. Which one is best will depend on
> analysing your particular business model.
>
I agree whole heartedly. That is why I recommend starting with a logic
structure before moving on to the physical.
--
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.comhttp://codeelixir.com
==================================================================
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: postgresql@aranya.com, darcy@druid.net, Curtis@daycos.com
Subject: Re: Table relationships
In-Reply-To: <bf05e51c0701090713v1564455esc175cf3bb402393c@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox