Deleting GraphQL node with xid (String @id) does not cleanup edges to that node

[jdgamble555 (Jonathan Gamble)]

I think you’re talking about two different things. The @cascade is not a workaround, but does solve your query problem. What you actually want, is a cascade on delete that just removes the connection(s).

This is a feature request that I made a while back. Hopefully we will see this one day, as this is how SQL handles the situation:

Feature Request: Cascade Delete & Deep Mutations By Reference Directive

Experience Report for Feature Request Update: 7/1/21 - to comply with Feature Request Template: What you wanted to do 1.) Update nested nodes from the parent Update Mutation. 2.) Delete nested nodes from the parent Delete Mutation 3.) Choose which nodes allow this Cascade Delete and Cascade Update, as not all parent / children relationships should have this ability What you actually did 1.) This can only be done by creating a new update mutation for EVERY SINGLE child individually. If I …

J