Does 2nd level caching work with Query and Criteria? The javadoc doesn't say anything and the documentation is vague and scattered about this.

Dino

Yes, if you excplicitely switch on query caching and if you use a cache implementation which suports query caching.

See the reference manul chapter 14.4. The Second Level Cache.

HTH
Ernst

Thanks. I was playing around with the caching. If I used 'get' based on the id it would cache it. But if I used criteria in conjunction with the setCachable flag it would not work (still need to figure this out; I'm using Ehcache which says it has query caching).

Let me describe what I'm doing and you can probably suggest a better way of doing it. In our app, we can't just lookup an object based on the id for security reasons. It has to be the id of the object plus the id of the associated organization. The results will never change (just as if I looked up an object by id). I know in hibernate 3.0, there is a notion of a filter. Is there anything for hibernate 2 (virtually every single lookup will have this additional check of organization id).

Dino

For the query cache configuration look for hibernate.cache.use_query_cache in the reference manual.

You're right that you will be able to solve this in H3 with the new filters. If you can wait, you bether stop reading here :-).

I solved a similar problem in H2 by making the organization id part of the primary key.
But this gives you an other problem. Foreign keys concist of only one field, but you would like to have two, the foreign primary key and the organization id.
You could try to solve this with views (maybe you need Oracle's instead of triggers).
In H2 you can easily have <many-to-one> proerties which include the origanization id, but you have to set update=false and insert=false. There are ways to make this associations updatable again but it's a hack.

You would have to map the foreign key in an extra property, which is writable. In an Interceptor.findDirty() (!) method you would have to patch this property if the association has changed. Dont' do this if you have other options, since it doens't stick to the API doc of the Interceptor, it's based on the internal implementation of the hibernate session which might change.

HTH
Ernst

I got all the caching strategies working. Thanks for the other advice as well.

Dino