Le vendredi 18 mars 2011 à 08:20 +, Grzegorz Jaśkiewicz a écrit :
> There's a generic trigger that sends a signal to a process whenever
> changes are made (via listen/notify mechanism), but when FK cascade
> fires it will cause a mass amount of notifies to be send out and I
> want to avoid it.
David J.
>
> -Original Message-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Grzegorz Jaskiewicz
> Sent: Thursday, March 17, 2011 6:41 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] triggers and FK cascades
David J.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Grzegorz Jaskiewicz
Sent: Thursday, March 17, 2011 6:41 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] triggers and FK cascades
Considering the foll
Considering the following example.
Tables A and B.
Table A contains some data.
Table B reefers to table A using FK with 'on delete cascade'. Table B
has a trigger on it, after delete per row
Now, is there any way I can tell in the trigger on table B that it has
been called from a direct delete on
