Dirk Jagdmann <jagdmann@gmail.com> writes:
> The idea behind the sample commands below is, that the whole deletion
> should be denied, because a trigger in a cascaded table blocked the
> deletion. The trigger works as expected and prevents rows with a value
> of "5" being deleted from table "b". However if the deletion was
> triggered via the cascaded foreign key (trigger), the deletion in
> table "a" is not rolled back, thus the row with "5" in "a" is lost.
> This of course leaves the database in an inconsistant state, because
> the foreign key in table "b" can no longer be referenced in "a".
> Now I'd like to know if this is a bug in the current form of cascaded
> deletions; or if this is desired behaviour and the oppression of
> deletions via triggers is undefined behaviour in the cascaded case; or
> if this issue just hasn't been addressed yet; or something completly
> differnt.
This is a bug in your trigger design. The database is doing what it's
supposed to do, ie, trying to delete the dependent row. If you turn
that into a no-op, it's your own fault if you don't like the resulting
state.
If you want the whole transaction rolled back, raise an error instead
of returning NULL.
(This has been discussed before ... see the archives.)
regards, tom lane
