Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thombrown(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Date: 2010-06-24 14:29:20
Message-ID: 201006240729.21260.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday 24 June 2010 7:21:04 am Grzegorz Jaśkiewicz wrote:
> because in my case I have many tables with FK pointing at foob. So
> writing that many triggers is going to be a royal pain.

I am trying to see how this is different from writing the triggers on the child
tables :) In any case are they not all pointing the at the same value in foob?
From what you have described you are trying to capture the name associated with
the id deleted in foob, so I am not sure why the child tables need to be
involved.

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Grzegorz Jaśkiewicz 2010-06-24 14:40:22 Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Previous Message Greg Smith 2010-06-24 14:23:21 Re: complicated running aggregate