Hibernate version:
3

Hi,

Is there any way to avoid database access if the second level cache is filled already ?

What I do is an initial load of all the objects I want to work with during my session. If a class then tries to load an object which is not in the cache yet (using a load() ), hibernate does a database lookup again. Can this be disabled ?

So what I need is something like a load()-method which only returns objects found in the cache (ignoring DB updates).

Any idea ??

Cheers,
Dirk

The only way I can think of is a custom load listener. That actually should not be to difficult, since if you extend the default listener it has a method specifically for retreiving entities from the database which you could just override.

Thanks for the reply,

that's actually the same conclusion I came to. But how can I tell hibernate to use the custom load listener ? (stupid question ?)

Cheers,
Dixie

It's me again,

an alternative approach I was thinking on is to get the EhCache out of the hibernate context (how ?) and ask the cache with the known name if it contains a given object.

But if I understand it right, the Cache.get(Object key) of EhCache does not take the Object itself as a parameter, right ?

Any idea on how to get the cache and ask it if it contains the given entity ?

Thanks in advance,
Dixie

I have the very same requirements. I'm my use case I'm loading data from a flat file where I need to check on several conditions to determine if the data is valid and the check involves looking up other domain data which I've configured to be cached. My problem too is that if a cache lookup is not found, the query is executed against the database (thereby losing the benefit of having a cache) and this dramatically increases to overall import time.

Could you kindly provide more details on how this can be solved.

Thanks,
Sanjiv