@pawan Hi. Just pitching in here. I feel that this is one of the most important features missing in Dgraph GraphQL right now and partial deletions are causing a lot of null references making a lot of GraphQL queries fail cause of few bad records.
I feel that it is better to have it as a slow operation to start with rather than not having it at all. Maybe, it can be optimized for performance at a later point in time since deletion operations are typically not frequent anyways.Just looking for ways to prevent bad records in the DB.
Or is there any other way you would avoid such situations? I use hasInverse to link all the schemas. Not sure how to avoid such issues which happen on situations like partial deletions, bad logic and so on affecting all records. Thanks.
