Re: Core Data: slow saves to persistent store
Re: Core Data: slow saves to persistent store
- Subject: Re: Core Data: slow saves to persistent store
- From: Jim Correia <email@hidden>
- Date: Tue, 16 Aug 2005 23:30:38 -0400
On Aug 16, 2005, at 11:23 PM, Jed Soane wrote:
Now if someone can give me a good explanation of why changing a
transient attribute should add a managed object to the update list
I'd be happy. Am I misunderstanding what transient attributes are?
One reason would be if you are using the "Delayed-Update Set
Accessor" pattern described here:
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdNSAttributes.html
If setting the transient attribute didn't mark the object dirty,
you'd never have a chance to recompute the persistent attribute
(using that pattern) and have the object saved.
In other circumstances, having it mark the object dirty may be over-
aggresive and "get in the way", but how is CoreData to know?
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden