@showDeleted would be a natural extension to this feature. I’ll edit my post above to include this.
And regarding specialized business-logic: Maybe the best solution that would cover all these little feature-requests (including this cascade-delete directive) would really be actual pre-/post-hooks written in golang. Maybe it’s just me, but I can’t make friends with the current state of @lambda directives. I still think that something that basic like timestamped soft-delete and cascade-delete should be implemented per default. Every other database has this.
Edit
Although isn’t @showDeleted perfectly handled by @auth currently (given some kind of deletedAt flag)? See my answer in your other thread. Of course having a @showDeleted directive makes this process a lot more transparent and less error-prone.