Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.2/8.9.1) with SMTP id PAA01306 for ; Tue, 2 Mar 1999 15:48:26 -0500 (EST) (envelope-from wieck@sapserv.debis.de) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@hub.org id m10HwAi-000EBRC; Tue, 2 Mar 99 21:53 MET Message-Id: From: jwieck@debis.com (Jan Wieck) Subject: Re: [SQL] Staus of Primary/Foreign key? To: stanb@awod.com (Stan Brown) Date: Tue, 2 Mar 1999 21:53:44 +0100 (MET) Cc: pgsql-sql@hub.org Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: <199903020436.XAA95816@hub.org> from "Stan Brown" at Mar 1, 99 11:35:57 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > 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. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #