Re: circular relationships URGENT

In article <58ldhsglfncjbdpoqqhq073t7iu1ej7tk2_at_4ax.com>,   Fernando <spamers_at_must.die> wrote:
> On Mon, 08 May 2000 10:21:47 +0200, Heinz Huber
> <Heinz.Huber_at_elbanet.co.at> wrote:
>
> >As I understand you, it is no circular relationship:
> >
> >customer 1 : n addresses
> >customer 1 : n orders
> >address 1 : n orders
> >
> >The relationship customer to orders is redundant, but might be kept
 for
> >performance reasons.
>
> Hhmmm... OK, but actually I have two types of addresses (billing and
> shipping), so I would have an n to n relationship. Any ideas about
> how to make it 1 to n? O:-)
>
> TIA
>
The tables in your design have to be related to each other based on PK and FK's so since you would have to store the address key for each applicable address into the order either at the header or detail level depending of if you want to support multiple bill to, ship to addresses per order. So I do not see the problem as there is nothing circular about the relationships you have described.

--
Mark D. Powell  -- The only advice that counts is the advice that
 you follow so follow your own advice --


Sent via Deja.com http://www.deja.com/
Before you buy.