Re: REFERENCES constraint - Mailing list pgsql-sql

From Josh Berkus
Subject Re: REFERENCES constraint
Date
Msg-id web-98845@davinci.ethosmedia.com
Whole thread Raw
In response to REFERENCES constraint  (Cedar Cox <cedarc@visionforisrael.com>)
Responses Re: REFERENCES constraint  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-sql
Cedar,

> 1. Can a column reference more than one table?  (This assumes you use
> a
> single sequence to generate the IDs for both "tbla" and "tblb".  I
> guess
> you would also have the problem of enforcing a unique index.  Say
> what?!  
> A unique index across multiple tables.. absurd :)  eg..
> 
>   CREATE TABLE blah (
>     id int4,
>     f_id int4 REFERENCES tbla (id) REFERENCES tblb (id)
>   )

I'd reccomend, instead, having blah reference tbla and tbla reference
tblb.  It'd have the same effect, without forcing you to monkey around
with custom triggers.

> 2. Can a column reference another column in the same table?  eg..
> 
>   CREATE TABLE bloo (
>     id int4,
>     p_id int4 REFERENCES bloo (id)
>   -- or
>   --p_id int4 REFERENCES (id)
>   )

Er ... why would you want to?

-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________                                      Josh Berkus Complete
informationtechnology      josh@agliodbs.com  and data management solutions       (415) 565-7293 for law firms, small
businesses       fax 621-2533   and non-profit organizations.      San Francisco
 


pgsql-sql by date:

Previous
From: Jeff Eckermann
Date:
Subject: RE: RE: Referencing named attribute in where clause doesn't work with7.1.2?
Next
From: "Alex Page"
Date:
Subject: Problem with aggregate functions and GROUP BY