Re: Ok, so refetch() is deprecated in EOEditingContext...
Re: Ok, so refetch() is deprecated in EOEditingContext...
- Subject: Re: Ok, so refetch() is deprecated in EOEditingContext...
- From: Kaj Hejer <email@hidden>
- Date: Thu, 6 Feb 2003 22:32:29 +0100
At 22:03 -1000 15-12-02, Art Isbell wrote:
On Sunday, December 15, 2002, at 06:40 PM, email@hidden wrote:
Can someone tell me the difference between:
refreshObject() and refaultObject()
and:
refreshAllObjects() and refaultAllObjects()
???
I will use refaultAllObjects() as recommended, but where would I
use the refreshObject()/refreshAllObjects() methods?
Since the refreshObject()/refreshAllObjects() method
descriptions are so ... ahem ... helpful, I'll have to guess based
on Apple's meaning of "refresh" in the
EOFetchSpecification.refreshRefetchedObjects() method. Normally, an
object already in the snapshot cache that is refetched either
explicitly or as the result of a fault firing will be discarded
rather than replacing the snapshot. So I'm guessing that
refreshObject()/refreshAllObjects() will replace existing snapshots
with refetched objects as if the fetch specification were set to
refresh refetched objects. It would be easy to write a simple WO
app that would test this hypothesis.
Hi!
Does anyone has found any more information about refreshObject than
the one in the api doc (which is almost like no documentation at all)?
One thing (I think) I should know :) but don't know is the difference
between ec.refaultObject(eo) and
ec.invalidateObjectsWithGlobalIDs(gids).
Does both this methods leads to the same result?
-Kaj :)
_______________________________________________
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.