Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

From: Thom Brown <thombrown(at)gmail(dot)com>
To: Grzegorz Jaśkiewicz <gryzman(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:43:27
Message-ID: AANLkTimcUk3ZShGC8Wcu8itdnsq-jsJLz0YkefHslywC@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/6/23 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
> I do understand what you are saying, but still it is highly
> unintuitive. Since trigger is BEFORE, developer will expect that data
> to be there.
>

Yes, I'm still not exactly sure why it's seeing uncommitted changes. :/

Thom

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Devrim GUNDUZ 2010-06-23 16:03:49 Re: missing uuid functions in postgresql-contrib RPM for linux?
Previous Message Grzegorz Jaśkiewicz 2010-06-23 15:41:13 Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE