Hi all,

A simple question: is it possible to make the results returned from Criteria read-only (i.e., with dirty-checking disabled)?

I'm using Hibernate 3.2 and my Criteria query returns a large number of results which won't be modified but only displayed to the user. I want to tell Hibernate not to create snapshots of all these results for dirty checking. There is a setReadOnly method on the Query interface to achieve just this, but there is no such method on the Criteria interface.

The funny thing is that Java Persistence with Hibernate, 2007 edition, gives an example of using the seemingly unexistent method on page 624..

My Criteria is rather complex, constructed programmatically, so I don't want to use HQL.

Thanks for any hints!

The method does indeed not exist, my hasty copy/paste error. Added to errata.

I was having the same question after seeing this in the same tome (great read btw). Is there any plans on adding this? I have the same type of issues, retrieving data that I know I don't want to update at this particular time.

Flushes and dirty checks are killing me, we typically end up calling the save() or update() when we know we're done modifying our entities but that seems to also force flushes even when in MANUAL flushMode. I've got a case right now where I ended up with a few thousands entities in my session yet I've got more than a million and a half calls to the onSaveOrUpdate events firing and the equals methods on all the objects are also getting hammered. I'm seeing those fire even if I simply load up some objects and then commit the transaction even though nothing in the session was modified at all.

Now, I'm currently looking at rewriting this to batch up the process a bit nicer but the code is very tangly and it would be nice in general not to worry about managed objects unless I called save or update.

Ok, while I would still love to have read only support on Criteria I figured out why I was still getting hammered with a MANUAL flushmode.

It would appear I didn't set it early enough in our framework so it didn't get set on the session, oops.

You can evict anything you want hibernate to forget about.

Yeah, I don't necessarily want to evict it as then I lose any lazy loading no?

Not to mention I'd rather not have to keep going back to the DB to load something that I might have already loaded in the session.