> On Jan 27, 2015, at 1:34 PM, Quincey Morris 
> <quinceymor...@rivergatesoftware.com> wrote:
> 
> FWIW, there is yet another way to get to backing store from a custom 
> primitive accessor — define another, private, Core Data property, and use 
> *its* primitive accessors. This may seem clunky, but it’s officially 
> countenanced in the Core Data Programming Guide, in the "Non-Standard 
> Persistent Attributes” section.
> 
> One advantage of this approach is that you can be sure there are no KVO 
> observers of the private property, so you can gleefully ignore KVO compliance 
> issues when doing housekeeping on the backing store value. Whether this makes 
> Core Data undo easier or harder is one of those things that I’m doomed never 
> to find out.

Thanks for the info. Right now I am trying to simplify a managed object 
subclass and replace non-standard attributes with standard ones without 
sacrificing performance. But this may come in handy sometime down the road. 

Richard Charles


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to