The cascading delete still doesn't handle the case involving dj.Part correctly. Basically, any deletion on dj.Part should cause deletion on its parent table. Marking deletion on the parent table then should cause appropriate cascading of deletion on the parent's as well as Part's subtables.