I hope this isn't a stupid question . . . I read chapters 10-15 on querying and it doesn't explicitly say whether entities returned by Criteria queries are persistent or detached. Chapter 10 notes that entities returned by Query.list() are persistent, but there is no mention of Criteria.list().

The problem we are having is that during a session in which we perform multiple Criteria selects with filters, some of the entities are being flagged as dirty and an attempt is being made to flush those changes between queries.

We have some overlap between the queries (a customer query loads a customer and its accounts, and an account query may load the same accounts) and I suspect that with the filters it looks like some of the collections are being modified. Since this is a query service we would like to operate in a read-only mode, but I've not seen anything in the Criteria interface to control this. The Query interface has a setReadOnly method that would be perfect except we need to use Criteria due to the dynamic nature of the queries.

Are Criteria results detached or persistent? Is there a way to control this? Is there something in the Criteria interface that is comparable to the setReadOnly method of Query?

Thanks,

Jesse

Has anyone ever responded to this question?

Is there any reason why Criteria doesn't offer setReadOnly method.

Is there any workaround to have the same behavior ?

Thank you,
Alain

I'm not sure if there's a valid reason for this or not. I do know that there isn't a hook to set it on the criteria and it always defaults to readOnly = false.

I clued into the setReadOnly after reading the new Hibernate book but apparently the example in there was a typo as the API didn't exist.

But digging into the source at the time I didn't see a reason why it couldn't be done but maybe there's a bigger technical reason that I didn't understand.