Re: CoreData - Fast Deletion Of Thousands Of ManagedObjects?
Re: CoreData - Fast Deletion Of Thousands Of ManagedObjects?
- Subject: Re: CoreData - Fast Deletion Of Thousands Of ManagedObjects?
- From: email@hidden
- Date: Wed, 21 Dec 2005 09:52:25 -0800
mmalcolm crawford wrote:
On Dec 20, 2005, at 7:21 PM, email@hidden wrote:
Might try to check the amount of relationships that need to
deleted and nullified by the original delete.
It might be complex, in which case there is not much to do except
hope for performance update or
maybe change your object model...
One thing, that *may* be slightly fast would be to call the raw C
array and cycle through that like:
Iterating over the C array will have an insignificant effect here.
There are several possible problems, including one known issue with
key-value observing notifications. The first step would be to
ensure that faults are not being fired as described in <http://
www.cocoabuilder.com/archive/message/cocoa/2005/12/20/152920> (see,
for example, Batch Faulting at <http://developer.apple.com/
documentation/Cocoa/Conceptual/CoreData/Articles/cdFetching.html#//
apple_ref/doc/uid/TP40002484-DontLinkElementID_19>). I hope I may
be able to address other issues soon.
I was thinking that according tot he above article saying: "You
should avoid executing multiple requests if you can instead combine
them into a single request that will return all the objects you
require."
How about the same thing for deletion? - (void)deleteObjects:(NSArray
*)objects error:(NSError **)error ?
Then coredata can optimize the deletion process?
_______________________________________________
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
_______________________________________________
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