I would like to specify a parameter called cascade:true in my delete mutation which will delete all related rows in other tables.
There's one way to specify this by configuring ON DELETE cascade constraint. (#225)
But it would be nice to have this as a parameter in my graphql mutation, if i have not setup those constraints in postgres.
I love this idea. It can be very useful :wink:
This is not easy to do (if it is possible at all). The dependency tree computation and its traversal are best left to Postgres with the cascade option in the foreign key constraint.
@0x777 is the cascade option something you can set?
@0x777 Don't worry, I found it -

Most helpful comment
@0x777 Don't worry, I found it -
