I have had good success using the Criterion API for pagination, but now I have come to the non-repeatable read issue where if the database is updated frequently while users are viewing paginated results, it will have the undesired effect of updating those results while paging through them.

Is there a way to fix the result set when it was first queried using the criterion API? A couple thoughts I had were to keep a datetime field of when the user first looked at the data and have that as part of my where clause to not get records newer than that.

Another thought was setting a read transaction boundary in the view tier and setting the isolation level to RR.

Does anyone have a best practice for this issue? Note that I am using JSF datatable in the front-end to display the Criteria's List results, so I don't think ScrollableResults will work for me as described in the docs.

Hibernate version 3.1.1.

Thanks,
Lou

Is there possibly a way to set the transaction isolation from the view tier declaratively?