From: | Richard Jones <rich(at)annexia(dot)org> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Referential integrity (foreign keys) across multiple tables |
Date: | 2006-07-24 08:59:07 |
Message-ID: | 20060724085907.GA19981@furbychan.cocan.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Sun, Jul 23, 2006 at 01:32:37PM -0500, Bruno Wolff III wrote:
> On Sat, Jul 22, 2006 at 14:32:57 +0100,
> Richard Jones <rich(at)annexia(dot)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?
Data integrity.
> 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.)
So if I get this right, I should use a trigger to ensure that the old
code causes the hostid field to be set in page_contents?
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Marques | 2006-07-24 11:28:44 | Re: Rows with exclusive lock |
Previous Message | Bruno Wolff III | 2006-07-23 18:32:37 | Re: Referential integrity (foreign keys) across multiple tables |