pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Josh Berkus <josh@agliodbs.com>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: Markus Bertheau <twanger@bluetwanger.de>
Cc: olly@lfix.co.uk
Cc: pgsql-sql@postgresql.org
Subject: Re: multi column foreign key for implicitly unique columns
Date: Wed, 18 Aug 2004 14:24:40 -0500
Message-ID: <20040818192440.GB21979@wolff.to> (raw)
In-Reply-To: <200408181005.13230.josh@agliodbs.com>
References: <1092734724.2627.4.camel@dicaprio.akademie1.de>
	<200408171945.15663.josh@agliodbs.com>
	<41235A90.1080300@Yahoo.com>
	<200408181005.13230.josh@agliodbs.com>

On Wed, Aug 18, 2004 at 10:05:13 -0700,
  Josh Berkus <josh@agliodbs.com> wrote:
> 
> I have my own issue that forced me to use triggers.   Given:
> 
> table users (
> 	name
> 	login PK
> 	status
> 	etc. )
> 
> table status (
> 	status
> 	relation
> 	label
> 	definition
> 	PK status, relation )
> 
> the relationship is:
> users.status = status.status AND status.relation = 'users';
> 
> This is a mathematically definable constraint, but there is no way in standard 
> SQL to create an FK for it.    This is one of the places I point to whenever 
> we have the "SQL is imperfectly relational" discussion.	

If users is supposed to reference status you can do this by adding a relation
column to users, using a constraint to force relation to always be 'users'
and then having (status, relation) being a foreign key.



view thread (38+ messages)  latest in thread

Message-ID: <20040818192440.GB21979@wolff.to>
Permalink:  ../20040818192440.GB21979@wolff.to/
Also on:    postgresql.org/message-id/20040818192440.GB21979@wolff.to

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: bruno@wolff.to, josh@agliodbs.com, JanWieck@Yahoo.com, twanger@bluetwanger.de, olly@lfix.co.uk
  Subject: Re: multi column foreign key for implicitly unique columns
  In-Reply-To: <20040818192440.GB21979@wolff.to>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox