Re: Referential integrity (foreign keys) across multiple tables - Mailing list pgsql-sql

From Bruno Wolff III
Subject Re: Referential integrity (foreign keys) across multiple tables
Date
Msg-id 20060723183237.GA22586@wolff.to
Whole thread Raw
In response to Referential integrity (foreign keys) across multiple tables  (Richard Jones <rich@annexia.org>)
Responses Re: Referential integrity (foreign keys) across multiple tables
List pgsql-sql
On Sat, Jul 22, 2006 at 14:32:57 +0100, Richard Jones <rich@annexia.org> wrote:
> 
> Now I want to add a column to page_contents, say called link_name,
> which is going to reference the pages.url column for the particular
> host that this page belongs to.

What are you trying to accomplish by this? The information is available
by doing a join. If you are trying to simplify things for applications,
you can probably do it with a view or rules depending on whether you
want to have an updatable view. If you are denormalizing for performance
and want constraints to maintain consistancy, then you probably want
to push the hostid down to page_contents as well as the url. These could
both be set with a trigger. (I think a rule could be used as well.)


pgsql-sql by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Rows with exclusive lock
Next
From: Richard Jones
Date:
Subject: Re: Referential integrity (foreign keys) across multiple tables