Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Thom Brown <thombrown(at)gmail(dot)com>
Cc: adrian(dot)klaver(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Date: 2010-06-23 15:31:40
Message-ID: AANLkTin79_wj1KcfqG56ikqIKxMh7zVYPmuG3nuFAoLz@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

it is confusing to me, because I thought triggers are firring BEFORE
anything goes away. So I assume that all data is still going to be
visible to the trigger, as it is firing BEFORE. The only thing is, it
looks like the FKs are doing the deletion and than things are handed
over to triggers.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-06-23 15:33:05 Re: High Availability with Postgres
Previous Message Thom Brown 2010-06-23 15:22:31 Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE