Re: Is NSEntityDescription insertNewObjectForEntityForName:inManagedObjectContext: this slow?
Re: Is NSEntityDescription insertNewObjectForEntityForName:inManagedObjectContext: this slow?
- Subject: Re: Is NSEntityDescription insertNewObjectForEntityForName:inManagedObjectContext: this slow?
- From: mmalcolm crawford <email@hidden>
- Date: Tue, 19 Jul 2005 00:37:52 -0700
On Jul 19, 2005, at 12:07 AM, Javigator wrote:
The entities can show up in a NSTableView (12 columns) powered by
an NSArrayController preparing the CoreData entities for it, but is
depended upon a master table (via binding the contentSet binding).
Now, when the contentSet binding is set to a master where no detail
data (= relationship objects) exists, and the app creates the 600
objects as described above, it takes its time (> 40 sec.). When the
detail table shows the relationship of another object and the
master currently getting the detail data is different, it doesn't
take more than 2 sec...
Then the application is presumably doing a lot of (largely
unnecessary) user interface update..?
Rather than setting a to-one relationship one object at a time, why
not wait until the end of the loop then add all the new objects to
the destination's to-many relationship?
mmalc
_______________________________________________
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