Re: FW: BUG in trigger and foreign keys - Mailing list pgsql-general

From Tom Lane
Subject Re: FW: BUG in trigger and foreign keys
Date
Msg-id 23364.1040789278@sss.pgh.pa.us
Whole thread Raw
In response to Re: FW: BUG in trigger and foreign keys  ("Jefim Matskin" <JefimM@sphera.com>)
List pgsql-general
"Jefim Matskin" <JefimM@sphera.com> writes:
> If try it with the same  script - but without the constraints - you will see the difference.
> And there should not be any since the data is the same in the tables.

No, it's not the same.  Consider the implications of the constraint
you added:

ALTER TABLE reseller ADD CONSTRAINT FK_reseller_parent
FOREIGN KEY (parent_id) REFERENCES reseller(reseller_id)
ON DELETE CASCADE ON UPDATE CASCADE;
^^^^^^^^^^^^^^^^^

This will cause the delete of reseller_id 1338 to propagate to the rows
in which 1338 appears as parent_id.  Which sure looks to me like it's
the behavior you're complaining of.

            regards, tom lane

pgsql-general by date:

Previous
From: Juraj Fedel
Date:
Subject: tools for design
Next
From: "Jefim Matskin"
Date:
Subject: Re: FW: BUG in trigger and foreign keys