From: | Dennis Gearon <gearond(at)cvc(dot)net> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | "Daniel R(dot) Anderson" <dan(at)mathjunkies(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Making Complicated References |
Date: | 2003-03-30 19:03:03 |
Message-ID: | 3E873F67.9000509@cvc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
How about some table definitions?
(amazing! what everyone else asked me for before they'd help me when **I** first
got here, now I ask others to supply :-)
Bruno Wolff III wrote:
> On Sun, Mar 30, 2003 at 03:06:46 +0000,
> "Daniel R. Anderson" <dan(at)mathjunkies(dot)com> wrote:
>
>>Hi all,
>>
>>I have tables A, B, and C. foo within Table B & C references foo in
>>table A. I want bar in table C to reference bar in table B -- but I
>>want it to reference only those bars in B with a foo that is the same.
>>
>>Is that possible?
>
>
> If foo + bar is a candidate key for B, then you can use a multicolumn
> foriegn key. If foo + bar isn't a candidate key for B, then I think you
> will need to explain more about what you are trying to do.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-03-30 20:19:19 | Re: System lockup |
Previous Message | Bruno Wolff III | 2003-03-30 18:19:51 | Re: Making Complicated References |