Using Entity Framework what is the difference between Cascade and ClientCascade?

Question

I am learning C# and how to use Entity Framework. I believe that I know what is Cascade, Restrict, NoAction and SetNull behaviors.

But there are other behaviors with the prefix Client:

I would like to understand what are the difference between them and when should I use ClientCascade instead of Cascade or ClientNoAction instead of NoAction.

Answer 1

the short answer is-- when dependent/ref. entities are loaded/cached in memory, the cascade delete action fails on the main entity - because a CYCLIC ref. LOCK.

ClientCascade allows the DBContext to delete entities even if there is a CYCLIC ref. LOCK