I read the links below and am still wondering: Could setting a Core Data attribute (e.g., person.name = @"Matt" cause a fault to fire?
I read the links below and am still wondering: Could setting a Core Data
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I read the links below and am still wondering: Could setting a Core Data attribute (e.g., person.name = @"Matt" cause a fault to fire?
Absolutely – reading or setting a Core Data attribute can cause a fault to fire. It’s easy to see how willRead would cause that (must go to the persistent store to get the data), and the willWrite ones seem to do the same (I could imagine it wants to compare what it’s about to write against what is actually there, to determine if there is actually anything to do at the
NSPersistentStoreControllerlevel).