Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.2/8.9.1) with ESMTP id PAA17750 for ; Thu, 11 Mar 1999 15:33:40 -0500 (EST) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id PAA20298; Thu, 11 Mar 1999 15:33:32 -0500 (EST) From: Bruce Momjian Message-Id: <199903112033.PAA20298@candle.pha.pa.us> Subject: Re: [SQL] Staus of Primary/Foreign key? In-Reply-To: from Jan Wieck at "Mar 2, 1999 9:53:44 pm" To: jwieck@debis.com Date: Thu, 11 Mar 1999 15:33:32 -0500 (EST) Cc: stanb@awod.com, pgsql-sql@hub.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > > > I have implemented referential integrity in older Postgres projects > > using functions. I am preparing to do a new project, aand was wondering > > what the status of Primary/Foreign key implementation was? > > > > I am starting with 6.4.2, > > I'm planning to implement most of the constraints currently > missing (foreign key, cascaded deletes) over rules - or at > least making the rule system capable of supporting it. > > But it will not be in v6.5. The reason for that is that > constraints need a special feature, the rule system currently > cannot support. It is required that rule actions can be > deferred until transaction commit time. At that time (or > when they should get run anyway), they need very special > visibility of heap tuples on a per range table base. One and > the same table might have to be scanned with different > snapshot's in one query. > > That all will take a while. I am glad to hear Jan say this. I hoped he had not given up on the idea of doing foreign keys. This is a major feature people are requesting. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026