On Tue, Jul 24, 2012 at 11:27 AM, Sean McBride <[email protected]> wrote: > Yes. My object is a subclass of NSObject and I don't override isEqual:. As > I test, I overrode it and always return NO. At first, I thought this did the > trick, since Core Data passed through this and saved properly; but alas, it > only seems to go through the path once after the document is opened, not > every time I ask it to save.
Are you still also triggering the KVO notices and/or using the setter? My thinking was that you probably need both things: first, to take an action that causes Core Data to notice you're changing the value (like calling -will/didChangeValueForKeyPath:), and second, that when Core Data compares the before and after values, that they are not -isEqual: to one another. (But, to be clear, this is untested supposition on my part.) _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
