Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A2D82475987 for ; Mon, 15 Apr 2002 16:37:06 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3FKavF26389; Mon, 15 Apr 2002 16:36:57 -0400 (EDT) To: Bruce Momjian Cc: Camila Rocha , pgsql-sql@postgresql.org Subject: Re: oid and oidvector In-reply-to: <200204151913.g3FJDTi10516@candle.pha.pa.us> References: <200204151913.g3FJDTi10516@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 15 Apr 2002 15:13:28 -0400" Date: Mon, 15 Apr 2002 16:36:57 -0400 Message-ID: <26386.1018903017@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/195 X-Sequence-Number: 7459 Bruce Momjian writes: > No, you can't use oid as a foreign key. You must use a PRIMARY column. Oh? regression=# create table foo(f1 int); CREATE regression=# create unique index fooi on foo(oid); CREATE regression=# create table bar (ref oid references foo(oid)); NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s) CREATE regression=# I agree with the advice *not* to do this, but that doesn't mean it can't be done. regards, tom lane