Re: refreshesRefetchedObjects significant hit on efficiency
Re: refreshesRefetchedObjects significant hit on efficiency
- Subject: Re: refreshesRefetchedObjects significant hit on efficiency
- From: Ray Ackland <email@hidden>
- Date: Fri, 19 Mar 2004 13:34:31 +1300
Jonathan,
This surprises me (which doesn't by any means mean that it is wrong). I
would have expected that turning on that option would mean it doesn't
need to make check to see if records have been modified, reducing the
amount of time. On the other hand, it would need to convert more
records into objects.
Perhaps the time difference will depend on how many records have been
altered since the last fetch - more records altered means increased
time (losing the benefit of not updating the changed ones) & fewer
records meaning less (saving on the checks while still creating all the
objects)? Also to consider is whether WO recreates an object if it
hasn't changed from database?
Just thought experimenting.
r.
On 19/03/2004, at 11:09, Jonathan Rochkind wrote:
It appears to me that setting 'refreshesRefetchedObjects' to true on a
fetch spec makes the objectsWithFetchSpecification call take
_significantly_ longer to return, for a result set of even a hundred
objects or so. It's a pretty significant difference, it can easily
double the time it takes to complete that method---more if you are
also using prefetchingRelationshipKeyPaths (which makes sense).
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.