Re: Triggering change notifications when modifying custom object ivars in core data app
Re: Triggering change notifications when modifying custom object ivars in core data app
- Subject: Re: Triggering change notifications when modifying custom object ivars in core data app
- From: Kyle Sluder <email@hidden>
- Date: Thu, 28 May 2009 12:31:58 -0700
On Thu, May 28, 2009 at 11:59 AM, Rick Hoge <email@hidden> wrote:
> The user can change the input parameters in the object's dictionary of
> inputs, and this should be reflected in the persistent store of
> corresponding to the custom attribute on disk. I realize this is ugly, but
> I can't think of any other way to do it given that the available operation
> classes are loaded as plugins at run time.
This is where you violate Core Data's assumptions. Instead of
mutating the dictionary, you need to provide a new one every time.
Or, you could have a "Parameter" entity, with two attributes: "key" and "value".
--Kyle Sluder
_______________________________________________
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