Re: Composite UNIQUE across two tables? - Mailing list pgsql-sql

From Jamie Tufnell
Subject Re: Composite UNIQUE across two tables?
Date
Msg-id b0a4f3350803070809x9da3b74oeaa20a75c2d14936@mail.gmail.com
Whole thread Raw
In response to Re: Composite UNIQUE across two tables?  (Jorge Godoy <jgodoy@gmail.com>)
List pgsql-sql
Hi Jorge,

On 3/7/08, Jorge Godoy <jgodoy@gmail.com> wrote:
> Em Thursday 06 March 2008 22:10:14 Jamie Tufnell escreveu:
> > I'm not sure how I would enforce that the site_group_id
> > added to the users table would correspond correctly with
> > the site_id (as per the sites table).  Perhaps I would make a
> > composite foreign key?
>
> Or you manage site_group_id from a trigger. When the user creates / chooses
> a site_id and updates/inserts this information then you fill site_group_id
> with a trigger. This way you guarantee the correctness of this parameter.

Hmm.  So your advice would be to duplicate the
site_group_id field into the users table as well?

That looks to be the consensus.. so I'm not sure why it feels
like I'm doing something wrong :-)

Thanks for your input!

J.


pgsql-sql by date:

Previous
From: "Jamie Tufnell"
Date:
Subject: Re: Composite UNIQUE across two tables?
Next
From: Markus Schatten
Date:
Subject: plpythonu + os.spawnv