Hello !

I am currently experimenting with hibernate for the first time.

We do have a self programmed persistence layer which maybe should be replace in the future.

One of the goodies with our layer is the possibility to programmatically create select/update/insert statements for the database (for sure, for some databases).
Much like your Criteria API.

To come to the point:
I think, i do not want to use Session.createQuery since this is too error-prone, and some developer might end in String operations to build the query.

Session.createCriteria is what i want, but i miss
.setCacheable(true) and .setCacheRegion()

hibernate debug and p6spy also showed me, that the same Criteria is executed to the database all the time.

do i misunderstand something here?

Just want to bring this up again!

I havent found any answer in the FAQ or Forum.

Thanks!
Mario

Criteria queries are not yet cacheable.

Might it be worth the time to dig into this, or do you have some technical reason (beside your spare time ;-) why this is currently not implemented?

I have already tried to understand the caching used with QueryCache.
Do you have a preferred direction how this sould be done?
Maybe, in the new year, i could try to implement/extend this to also allow this caching for the CriteriaAPI.

Ah, its on the TODO list, but so are *lots* of other things. Look at the current v21branch in CVS, and you can see how it is done for both SQLLoader and QueryTranslator. It should be reasonbly straightforward to extend the same thing to CriteriaLoader.

But make sure you work from current CVS, not from the source in 2.1final!

Here one could find the patch against v21branch to add the cacheable/cacheRegion to the Criteria API.

http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-660

Hope i have understand things right, comments are welcome.