{quote:m4ktub}Something in the lines of{quote}

Woa... I think you may be getting near to the level of .Net's LINQ with that OQL query (OQL is not and should not be new to me, but I just could no resist throwing that one).
Read {link:.Net's LINQ|http://msdn2.microsoft.com/en-us/library/ms364068(vs.80).aspx} for some examples (thanks Mr. ~~<censored>~~ for that).

From what I read, you created a collection of pages (as in page 1, records 1-10, page 2, records 11-20 and so on). Then you materialize the elements by iterating the page elements? Am I understanding correctly?

If so, wouldn't it be better to have a

{code}
Query.pagedExecute(Class c, String query, int begin, int offset, Object... params);
{code}

{quote:pabrantes}Does this really makes sense? Shouldn't be the persistence framework a small set of operations and then you would create more complex operations - such as paging - around it?{quote}

My € 0,02 is that paging is something you will be wanting to do at database level...