X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A4D4ED1B42F for ; Tue, 23 Dec 2003 13:20:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 78730-10 for ; Tue, 23 Dec 2003 09:19:27 -0400 (AST) Received: from noon.pghoster.com (noon.pghoster.com [64.246.0.64]) by svr1.postgresql.org (Postfix) with ESMTP id 8491CD1C961 for ; Tue, 23 Dec 2003 09:19:24 -0400 (AST) Received: from [61.5.0.182] (helo=winxp) by noon.pghoster.com with asmtp (Exim 4.24) id 1AYmRa-0002vi-Nf; Tue, 23 Dec 2003 07:19:27 -0600 Message-ID: <034e01c3c957$508902c0$52285e3d@winxp> From: "Chris Travers" To: "Pedro" , References: <6.0.1.1.2.20031213220735.01c8dec0@mail.captech.no> <3fe39013$0$6978$7a628cd7@news.club-internet.fr> Subject: Re: INHERITS and Foreign keys Date: Tue, 23 Dec 2003 20:13:04 +0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - noon.pghoster.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - travelamericas.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/164 X-Sequence-Number: 16330 Hi Pedro; I understand that at the moment it is more of a design limitation than a bug. I think we should vote the desired behavior as a feature request, however. Best Wishes, Chris Travers ----- Original Message ----- From: "Pedro" > >> Foreign keys, unique and primary key constraints do not meaningfully > >> inherit currently. At some point in the future, that's likely to change, > >> but for now you're pretty much stuck with workarounds (for example, using > >> a separate table to store the ids and triggers/rules on each of the > >> tables > >> in the hierarchy in order to keep the id table in date.) > > hi > > same problem here on 7.4 > can we vote for this bug somewhere ?! > > thanks for your time > Pedro > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > >