I thought the object existed only in the session? So if I did a
query it'd go:
Get key list form query cache.
Satisfy Object list from session cache (if possible).
Else hit the database.
If I happened to have the objects in question in my session, I could
avoid the database hit. If you happened to do the original query though in
your session, then I'd have to pull the objects out of the database wouldn't
I?
> -----Original Message-----
> From: Henri Dupre [mailto:[EMAIL PROTECTED]
> Sent: Saturday, September 24, 2005 9:12 AM
> To: Patrick Casey
> Cc: Tapestry users
> Subject: Re: Hibernate session model
>
> On 9/23/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > I rather have a DB Query than a lazy exception. And not for every
> call!
> > > The hibernate cache is here for that.
> >
> > If memory serves, the hibernate cache caches keys, not objects.
>
> This is not true. The hibernate second level cache is a map with <key,
> object>,
> If your key is found in the cache then it retrieves the object (memory
> or file depending on your cache configuration).
> We achieve a high performance by having it properly configured on a
> per-class basis even with complex queries.
>
> Henri.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
