poor hijacked thread.
You cannot ask -executeFetchRequest: to either filter (by predicate)
or sort (by sort descriptor) based on a transient or unmodeled property.
The table view and array controller can happily sort or filter in
memory. Performance on sorting large data sets in memory lea
I don't mean to hijack this thread, but I have had a related (?)
problem where a transient String attribute is derived from a
persistent Binary attributed (an archived NSAttributedString). When
my NSTableView sorts on this column, and I modify a managed object
displayed in the table, I get
On Jan 26, 2009, at 2:09 PM, jonat...@mugginsoft.com wrote:
The docs do state (Core Data Guide - Faults and KVO Notifications)
that KVO notifications do occur as faults are realised, even if
the faulted relationship is already in the moc (is this last
assumption correct?)
I'm not sure wh
On 26 Jan 2009, at 21:23, Ben Trumbull wrote:
On Jan 26, 2009, at 11:47 AM, jonat...@mugginsoft.com wrote:
Why ? Put Shark in Time Sample (All Threads State). You'll get
close to wall clock time with a sampling accuracy of microseconds.
36000 years later...
I'm not that old. For shor
On Jan 26, 2009, at 11:47 AM, jonat...@mugginsoft.com wrote:
Why ? Put Shark in Time Sample (All Threads State). You'll get
close to wall clock time with a sampling accuracy of microseconds.
36000 years later...
I'm not that old. For short events like launch time, I've found Shark
to
On 25 Jan 2009, at 21:30, Ben Trumbull wrote:
The results for a default fetch on a data set of 1500 very simple
objects are:
XML - usesLazyFetching = NO 38.00 sec load
XML - usesLazyFetching = YES 4.78 sec load
SQLite - usesLazyFetching = NO 35.25 sec load
SQLite - usesLazyFetching = YES
On 24 Jan 2009, at 18:41, Matt Neuburg wrote:
On or about 1/24/09 10:17 AM, thus spake "jonat...@mugginsoft.com"
:
I am also having horrible performance problems.
A data set of 1500 items with a total on disk size of 1.8MB is
taking
more than 30 secs to load.
Maybe NSArrayController -fetchW
