Re: many junction tables

From: Arne Weiner <aswr(at)gmx(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: many junction tables
Date: 2001-09-04 16:27:33
Message-ID: 3B9500F5.E9F97B12@gmx.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


I don't understand what exactly your problem is. What
what makes me unsure is: why do you want to store the
target table names in the association table?

Eric Kolve wrote:
>
> I was wondering if anyone has a solution to the following problem. I
> have a few tables similar to the following.
>
> person_table
>
> city_table
>
> company_table
>
> If I want to associate a person with a one or more cities. I need to
> create a city_persons table that contains just the primary keys of both
> the city_table and person_table. If I want to associate a person to
> many companies, I have to do a similar thing. Now, if I wan to
> generalize these associaes I can create something like an associate
> table which will contain both id's plus two columns which indicate the
> source and target tables of the relaionship. Does anyone have
> suggestions along these lines on how to generalize such relationships?
>
> thanks,
>
> --eric
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert J. Sanford, Jr. 2001-09-04 16:35:57 Re: PL/java?
Previous Message Bruce Momjian 2001-09-04 16:15:51 Re: [WAY OT] Re: PL/java?