Re: cache in memory
Re: cache in memory
- Subject: Re: cache in memory
- From: Mike Schrag <email@hidden>
- Date: Wed, 11 May 2005 21:50:58 -0400
These are the rules that EODatabase uses to determine when to use the
object cache to evaluate a fetchspec:
if(!_flags_ignoreEntityCaching && eoentity.cachesObjects() &&
eofetchspecification.isDeep() &&
_validateQualifierForEvaluationInMemory(eofetchspecification.qualifier
(), eoentity))
1) _flags_ignoreEntityCaching = I'm checking when this is true, but
it appears to be an internal flag that is only set when the cache is
changing, so we can assume this is probably ok
2) eoentity,cachesObjects() = obvious one, the assumption is that
this is returning the correct value, though it's worthy of a check :)
3) eofetchspecification.isDeep() = This is very interesting and I
think it's off for my fetch spec! So this quite possibly could be
screwing me
4) _validateQualifierForEvaluationInMemory = This is implemented as
you would expect -- And's and Or's must be composed entirely of
qualifiers, and all the keys must be attributes defined in the class
description
So I'm off to look more into this isDeep restriction to see if this
might be toying w/ me.
ms
On May 9, 2005, at 12:12 PM, Chuck Hill wrote:
On May 8, 2005, at 5:23 PM, Mike Schrag wrote:
So basically to traverse this graph, I would have expected TWO
queries, and instead I see lots of them. Is there anything else I
should be setting? Are there any development commandline flags
that might be set that would override the requested behavior?
(WOCachingEnabled is strictly the WOs, not EO, right?).
_______________________________________________
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