From: jwieck@debis.com
To: stanb@awod.com
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] Staus of Primary/Foreign key?
Date: Tue, 2 Mar 1999 21:53:44 +0100 (MET)
Message-ID: <m10HwAi-000EBRC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <199903020436.XAA95816@hub.org>
>
> 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) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jwieck@debis.com, stanb@awod.com, pgsql-sql@hub.org
Subject: Re: [SQL] Staus of Primary/Foreign key?
In-Reply-To: <m10HwAi-000EBRC@orion.SAPserv.Hamburg.dsh.de>
References: <199903020436.XAA95816@hub.org> <m10HwAi-000EBRC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox