Re: cache in memory
Re: cache in memory
- Subject: Re: cache in memory
- From: Chuck Hill <email@hidden>
- Date: Sun, 08 May 2005 17:03:39 -0700
Unless something has changed, the docs are correct. The first reference to
any of the entity's objects will fetch all such objects into memory. Any
subsquent fetches or fired faults will only go as far as the snapshot
layer. There should be no further DB access. I've verified this recently
with 5.2.3.
Are you perhaps using a fetch spec with "refreshes refetched objects" set
to true? I'm not sure what would happen in that case.
Chuck
At 07:13 PM 08/05/2005 -0400, Mike Schrag wrote:
>So the docs for "cache in memory" on an entity make it sound like WO
>won't need to hit the database again after the first full load. I'm
>not seeing this behavior at all, though, which leads me to believe
>I've misunderstood this flag. Even with cache in memory, I still see
>queries to retrieve entities of the particular type that i flagged.
>What is the actual definition of this field?
>
>ms
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
e.net
>
>This email sent to email@hidden
>
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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