Re: 1 foreign key to 2 different tables? - Mailing list pgsql-general

From Bruno Wolff III
Subject Re: 1 foreign key to 2 different tables?
Date
Msg-id 20040502013955.GA29213@wolff.to
Whole thread Raw
In response to Re: 1 foreign key to 2 different tables?  ("Ryan Riehle" <rkr@buildways.com>)
Responses Re: 1 foreign key to 2 different tables?  ("Ryan Riehle" <rkr@buildways.com>)
List pgsql-general
On Sat, May 01, 2004 at 18:09:34 -0400,
  Ryan Riehle <rkr@buildways.com> wrote:
> For what I am reading now it looks like this is an opportunity to use CREATE
> ASSERTION, but this functionality appears to be unstable so far and is not
> recommended for production environments.  Is this correct?   Otherwise, can
> someone post an example of implementing a check constraint or trigger since
> I have not created a check onstraint that is above common complexity and and
> have never tried a trigger.

The simplest way to do this is probably be to use two separate fields
to make the references and make sure exactly one of them is nonnull.
You also might want to rethink your design. That you want to do this
suggests that there is something odd about the schema design you
have come up with.

pgsql-general by date:

Previous
From: "Ryan Riehle"
Date:
Subject: Re: 1 foreign key to 2 different tables?
Next
From: Tom Lane
Date:
Subject: Anyone interested in a Pittsburgh-area Postgres users' group?