From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Michaël Lemaire <adminsys(at)rodacom(dot)fr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Delete triggers order in delete cascade (pg 8.3.7). |
Date: | 2009-07-02 12:14:21 |
Message-ID: | 4A4CA49D.8000600@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michaël Lemaire wrote:
> Hi all.
>
> I've come across a problem with delete cascade.
>
> I have three tables A, B and C.
> Table B has a foreign key on A with delete cascade.
> Table C has a foreign key on B with delete cascade.
> So, we have this reference chain: C->B->A
> All three tables have an 'on delete' trigger.
>
> My problem is, when I delete a row from A, the delete triggers are
> fired in the order A then B then C, which is the opposite of what I
> expected (the row from B should be deleted before the A one, or the
> reference constraint would break).
The "on delete cascade" are (sort of) implemented with system triggers.
So deleting a row from A triggers a delete on B where fkey=X and so on.
> This happens with 'after' and 'before' triggers.
> I really need the order to be C then B then A.
Why? What are you trying to do?
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Reid Thompson | 2009-07-02 12:42:43 | Re: Does anyone know of a job scheduler that uses PostgreSQL? |
Previous Message | Greg Stark | 2009-07-02 11:27:57 | Re: 1 Sequence per Row i.e. each customer's first order starts at 1 |