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.
// Save changes if any.
NSError *error;
if ([managedObjectContext hasChanges] && ![managedObjectContext save:&error]) {
// TODO: handle this error better.
NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
abort();
}
That depends. If you’re sure that changes have been made to the
managedObjectContext, then there’s no need to check. However, if there’s any possibility that changes have not been made, then you should check before saving.Check out the application delegate of the CoreDataBooks Xcode sample app for examples of both these scenarios.