You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a question and not an issue. I'm trying to understand the difference between MR_save and MR_saveNestedContexts. Looking at the names, I would assume MR_save is equivalent to NSManagedObjectContext's save: method, and MR_saveNestedContexts saves all children contexts up to the root which then persists to the store. But looking at the source, it looks like both methods are doing the same recursion up to the root, and therefore persisting to store.
So the questions is if I only want to save a child context up one level (not to the root context), should I use save: or MR_save?
The text was updated successfully, but these errors were encountered:
In the latest version MR_save just calls MR_saveWithErrorCallback:, which will just save the current context, without any recursion. So the answer to your question would be that you can use eater of those two, although MR_save is a bit more convenient and powerful.
This is a question and not an issue. I'm trying to understand the difference between
MR_save
andMR_saveNestedContexts
. Looking at the names, I would assume MR_save is equivalent to NSManagedObjectContext'ssave:
method, andMR_saveNestedContexts
saves all children contexts up to the root which then persists to the store. But looking at the source, it looks like both methods are doing the same recursion up to the root, and therefore persisting to store.So the questions is if I only want to save a child context up one level (not to the root context), should I use
save:
orMR_save
?The text was updated successfully, but these errors were encountered: