Problem:

I use paging with setMaxResult() and setFirstResult() in my application, and the pagination works, but, i have a problem when the database was updated.
I need to solve it, but i don't have idea, can any help me

You question is not very clear..

but if the database is updated, you refresh will include the new results. Thats very desired.

what some people do is, get ALL the results at one time, and then use pagination on those stored results. These results can sit in some kind of cache, or session or request scope, wherever they find it should be at.

HTH

Scuse me, but, i erase in the previous post same data... :)

My problem is that when i paging data, if other user update the database, then, i need to show consistent refresh.

Your solution of get all the results at one time, is very expensive, and i need a scalable solution.

Thank you for all, and i hope that you and other understand my now.

Regards
epsino

PD: Mi english is very poor :-P

You can user ScrollableResults

regards

I read that the ScrollableResult not is good, and is not recomended, it is true

ScrollableResult needs an open session as iterate

I think that history from setMaxResult and SetFirstResult is from mysql or postgresql LIMIT clause (not in sql standard)
They do query like :
parse
bind
fetch all rows

When we have big table all rows can't be in memory and guys from MySQL and Postgersql add LIMIT (postgresql have cursor now and do work like oracle)

Oracle do next (this is correct way for query)
parse
bind
fetch one or more rows (but no all)

We don't need limit - we only return rows which we want

Hibernate emulate LIMIT on oracle with query and use rownum, but it isn't necessery - we can use every query and return any rows

ScrollableResult is better way for this, but I don't know is it work in Hibernate

regards