Commented by: Smirnoff Serg (wildsery)

I think this is not a bug.
Master must be deleted first 'cause if other transaction inserting details records of same master, it checks FK okay, while you delete only your details, and may commit them.
Your subsequent deletion of master will fail - new details remaining.

Commented by: Valdir Stiebe Junior (ogecrom)

It is the same behaviour as if in a first transaction we insert detail records and in a second transaction we try to delete the master. The "Foreign key references are present for the record" exception is raised.

But I agree that if I first tried to delete the master, this operation must have more priority than the inserts in other transactions.

I've filled this issue because of the trigger order and the visibility of the master record in the before delete detail trigger.

Commented by: @hvlad

It's as designed and not a bug

Commented by: Philip Williams (unordained)

Is the suggested work-around, then, that rather than relying on on-delete-cascade, you should put a before-delete trigger on the master record which deletes any detail records, thus allowing the detail table's before-delete triggers to still see the master record?