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: Adam Knight <email@hidden>
- Date: Tue, 16 Aug 2005 23:10:14 -0500
On Aug 16, 2005, at 10: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?
Understand what they are, first. They're not ivars; they're
variables you want undo/redo on but don't want to save. In general,
if you don't want the variable in the store and it doesn't need to be
a part of the undo stack, make it an ivar instead of a transient
value (most calculated values should just be ivars and/or methods).
Doing so also gets rid of the common "I just opened my Core Data
document and it's already dirty!" problem: your calculated value
changed from nothing to something and, ta da, you're dirty.
/bitter because he found this out an hour ago and has been chasing it
for a week.
Adam Knight
will bug code for food
http://www.codepoetry.net/
I ♥ my
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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