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: pgsql-general(at)postgresql(dot)org
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Date: 2010-06-23 13:50:31
Message-ID: AANLkTik0SYgfg_ezIyLxRYoVSQOvdMYt6Ok64tG6wA-f@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>:
> this is 8.3.7, for the record. And no, They won't let me update it to 8.3.11 :/
>

Well, same applies:
http://www.postgresql.org/docs/8.3/static/sql-createtrigger.html

I've just run the same set of statements you specified against 8.4.1,
8.4.4 and 9.0 beta2 and the same thing happens:

NOTICE: foobarred <NULL>
CONTEXT: SQL statement "DELETE FROM ONLY "public"."fooa" WHERE $1
OPERATOR(pg_catalog.=) "foob""

Thom

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Grzegorz Jaśkiewicz 2010-06-23 13:52:32 Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Previous Message Bruce Momjian 2010-06-23 13:48:49 Re: Problem serving one-click installer to Syria