eosharededitingcontext & in memory fetching
eosharededitingcontext & in memory fetching
- Subject: eosharededitingcontext & in memory fetching
- From: "Jonathan Fleming" <email@hidden>
- Date: Tue, 24 May 2005 18:10:48 +0100
Very quickly, I have read in Apple's docs that when using
eosharededitingcontext any normal fetches (i.e. using a fetchSpec) that you
have will first look in the eosharededitingcontext for the queried objects
and if any or some of the objects are not here only then it will move on to
do a full fetch from the database, however, sometimes I feel as if the
application is doing a full fetch regardless as it seems very slow to
respond with objects that have actually already been fetched in the shared
context. Other times the app runs nice and fast as if it had done an
in-memory search.
If I have NSArray's such as allSharedTbNavPages, allSharedTbNavPageContents,
allSharedTbCategorys in my Application.java as a result of the shared fetch,
should I be creating a different sort of fetch against the items in these
arrays such as a filtered in-memory fetch or am I correct in having a normal
fetchSpec and allowing the app to do it's thing... somehow I feel i'm
missing something.
Can anyone point me to good examples of how to do a proper in-memory fetch,
correctly
Kind regards
Jonathan :^)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden