pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: cnliou@eurosport.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Foreign Key Constraint Deletion Order
Date: Tue, 20 Nov 2001 00:09:26 -0800 (PST)
Message-ID: <20011119235947.T53451-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <200111200350.0341@lh00.opsion.fr>

On Tue, 20 Nov 2001 cnliou@eurosport.com wrote:

> This is really a pain though it works.
>
> Since delete from PurchaseMaster and PurchaseDetail
> are both possible, two subtraction trigger functions
> must be written for PurchaseMaster and
> PurchaseDetail, respectively.
>
> It also seems unwise not to use the
> powerful-but-easy-to-use RI capability (on delete
> cascade on update cascade) but to implement it with
> my own trigger to be fired by PurchaseMaster.

Yeah, there's also some locking gotchas involved
so while the RI stuff isn't nearly perfect it's
probably a good idea to stick with it unless
you're running one of the problem cases.

> If the delete was always done on PurchaseDetail
> before PurchaseMaster, then one subtraction function
> for PurchaseDetail along with the RI would settle
> down everything.
>
> Am I asking for too much, or RI and triggers were not
> designed for operations like this example in the
> first place?

For the particular case you're looking for I don't think
so.  It sounds like it'd make sense, but I don't think
it'd fit the spec wording (given that we've been arguing
how far after the deletion that the cascade occurs, I
don't think anyone's argued for before the deletion).





view thread (8+ messages)

Message-ID: <20011119235947.T53451-100000@megazone23.bigpanda.com>
Permalink:  ../20011119235947.T53451-100000@megazone23.bigpanda.com/
Also on:    postgresql.org/message-id/20011119235947.T53451-100000@megazone23.bigpanda.com

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: sszabo@megazone23.bigpanda.com, cnliou@eurosport.com
  Subject: Re: Foreign Key Constraint Deletion Order
  In-Reply-To: <20011119235947.T53451-100000@megazone23.bigpanda.com>

* 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