Re: Recomputing non-standard Core Data attributes when child MOC is saved?
Re: Recomputing non-standard Core Data attributes when child MOC is saved?
- Subject: Re: Recomputing non-standard Core Data attributes when child MOC is saved?
- From: Dave Fernandes <email@hidden>
- Date: Wed, 19 Jun 2013 01:42:34 -0400
The foolproof way to do it is to have the transient attributes recalculated each time they are accessed. In other words, they are simply getter methods. But if they are expensive to compute, this might not work well. If you are using bindings or KVO, you then have a class method + (NSSet*)keyPathsForValuesAffecting<AttributeName> that ensures observers of the transient attribute are notified when underlying non-transient attributes change.
On 2013-06-18, at 10:08 PM, Rick Mann <email@hidden> wrote:
>
> On Jun 18, 2013, at 19:07 , Laurent Daudelin <email@hidden> wrote:
>
>> Just a wild guess but what about awakeFromInsert?
>
> Well, I think that only gets called when you first create the object. In my case, objects already exist.
>
> --
> Rick
>
>
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden