Received: from smtp011.mail.yahoo.com (smtp011.mail.yahoo.com [216.136.173.31]) by postgresql.org (8.11.3/8.11.4) with SMTP id f78Hg5647370 for ; Wed, 8 Aug 2001 13:42:05 -0400 (EDT) (envelope-from janwieck@yahoo.com) Received: from jupiter.us.greatbridge.com (65.196.69.55) by smtp.mail.vip.sc5.yahoo.com with SMTP; 8 Aug 2001 17:42:03 -0000 X-Apparently-From: Received: (from wieck@localhost) by jupiter.us.greatbridge.com (8.11.2/8.11.2) id f78HoqJ11933; Wed, 8 Aug 2001 13:50:52 -0400 From: Jan Wieck Message-Id: <200108081750.f78HoqJ11933@jupiter.us.greatbridge.com> Subject: Re: REFERENCES constraint In-Reply-To: from Josh Berkus at "Aug 8, 2001 09:29:17 am" To: Josh Berkus Date: Wed, 8 Aug 2001 13:50:52 -0400 (EDT) CC: Cedar Cox , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/134 X-Sequence-Number: 4355 Josh Berkus wrote: > 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. Nobody said that primary keys are limited to the serial datatype. So in case that tbla and tblb could have different sets of keys with a possible intersection, and further given that blah.f_id shall be limited to values both have in common, there's no other way than having multiple foreign key constraints on that one column. Thus, it is possible. I'm not sure if the above syntax is supported, but at least you can put table level CONSTRAINT clauses into the statement and/or add the constraints later with ALTER TABLE. > > > 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? To build a tree structure of nodes. Root nodes have p_id (meaning parent-id I guess) set to NULL, all others must have an existing node as parent. Together with ON DELETE CASCADE it'd build an expert-directory-structure (experts usually have "alias rm='/bin/rm -rf'" in their .profile, you know). Again, since it makes sense it is possible. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com # _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com