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:46:36
Message-ID: 201006240746.36548.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday 24 June 2010 7:40:22 am Grzegorz Jaśkiewicz wrote:
> that Id refers to 'name' column that I need. There still is FK on it,
> so basically it is broken inside transaction, from trigger's
> perspective.

I understand this part. What I am saying is think about reversing your point of
view. Instead of pulling the information from foob, push out the information
from foob.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-06-24 14:48:04 Re: Could not locate a valid checkpoint record
Previous Message Grzegorz Jaśkiewicz 2010-06-24 14:40:22 Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE