Understanding Core Data delete rules on One to Many

I am a little fuzzy about Core Data Relationships deletion rules. So if someone could help me answer a few questions about them.

I have Entities A and B. A has a to-Many relationship with B, and B has a to-One relationship with A.

A<--->>B

Now, if I set the delete rule at A to Cascade, I understand it will delete all the Bs related to it. But if I set it to Nullify, will it set the Bs to NIL or just the Foreign Key to Nil?

And I looked everywhere about the relationship from B to A, should I set it to Nullify? Will that just Nullate the "B Object" at A? Or will it Nullify all the Bs associated with A? What about Cascade? Will it delete all the Bs associated with A, or just the particular B?

Or do I just use "No Action" on the relation from B to A so that when I delete B, no change will happen to A, but the reference to B won't exist?

I am PRETTY confused with these, so excuse my questions.

Thanks.

If you set the delete rule to "nullify" and delete the A object, then the references to that object in the Bs will be removed. The inverse works the same way. If you have cascade and delete B then it will remove the A that B pointed to. It will then follow the delete rule from A to the remaining Bs (either cascade or nullify).

The rules you set really depend on your data model. If A were a customer and B were their orders then you could set the A->B rule to deny (prevent A from being deleted if it the customer has orders) or cascade (delete the orders when the customer is deleted). The B->A rule would probably be "nullify". If an order is deleted simply remove the reference to the order from the customer.

The relationship delete rules are described in the Apple Core Data Programming Guide

More deep explanation and visualization with delete rule.

---

Let be assume we have database with table person and work. Single person can have many tasks to do.

> Sample data and ER relationship

>

---

Delete Rule Explation

1. No Action : If I add this delete rule on relationship and then delete one of the person then it will not do anything with the task but person got deleted. The task still points to the person that we deleted.

• Use Case: I don't think it is used anywhere.

2. Nullify : If I apply this delete rule and delete the person then associate tasks will points to the null person. For example, I deleted the thor and thor tasks will point to the null person. Check below output.

• Use Case : Let's assume we have DB with Person and address. Now person sells his house to broker. In this case you can null the person of that address and reassign the owner to that house when new Person purchased that house.

3. Cascade : In this rule, if I deletes the person then it will deletes all the tasks associated with that person. For example, I deletes the Spiderman, check below output.

• Use Case: Let be assume we have a user and his friends list. If user account deleted then we also want to delete the friend list.

4. Deny : Now we have person i.e. IronMan with 2 tasks. In this rule, if I try to delete the Iron Man then it does not allow me to do. It gives error "The operation couldn’t be completed. (Cocoa error 1600.)" on saving the context. Now to delete the Iron Man person, we need to delete all his associated tasks and then we could able to delete the Person.

• Use Case: Lets assume, there is a user with bank account. We can not delete the user from the bank until his account is not closed.

---

if you set "nullify" and delete A's object , A's object and the back relationship only will get deleted not B's object.

eg : Customer entity has nullify relationship to orders . and if you delete a customer from customer entity, it will just delete customer and its back relationship from order . it wont remove the orders the customer made

but if the relationship is "cascade" it will remove the customer and his orders .

if it is "deny" . if the customer has any order , it wont delete delete the customer even .