Save Only the Object

[matrinox]

This can be achieved by having exactly one MOC per object but I'm not sure of the implications in both using it and coding it. Would there be huge memory implications? Would this have to be a special condition, like fetching an object with a hasOwnManagedObjectContext flag set to yes? Are there alternatives to this, perhaps when calling save creating a child MOC, saving that, and merging back into the original MOC?

[stephencelis]

Hm, could you please provide more information on some examples of why you'd want to do that in your application?

I actually wonder if it makes more sense to remove the -save method entirely, as it's confusing right now (and obj.managedObjectContext save: is not too difficult to remember/type).

An alternative might be the idea of block-based transactions, where updates that happen in the block are done on a new child context, and when the block completes it saves the context, then merges it back into the main context.

[supermarin]

@stephencelis given the path of decoupling from CoreData, i'd still keep this one in.

[matrinox]

The example I can think of is saving a nested attribute without saving the parent (e.g. saving contacts without saving profile).

Block transactions seems like a good implementation.

Also I agree that current -save is misleading and really just a shorthand. That's why I think it's a great use for individual object saving.