True, it didn't work with groupBy. Also it's often misused and misunderstood. It never used any database specific tricks to make it perform better - just brute force.
By the way, internally queryForPaginatedList used the overload for queryForList that accepts skip and max parameters. You can continue to use that method to implement your own paginated list function if you wish - although doing it with the database specific methods is far more efficient. Jeff Butler On Dec 10, 2007 10:28 AM, Chetan Nayak <[EMAIL PROTECTED]> wrote: > I think the reason for it to be deprecated is because it does work with > Group By Clause........Im just guessing here > > > On 12/10/07, Stefano Tranquillini <[EMAIL PROTECTED]> wrote: > > > > Tnx > > so i've to made the pagineted query by myself. > > and, if i extract all the results and show only the result beteween an > > interval is the samething? > > PS: why paginated list has been deprecated? > > regards > > > > On Dec 10, 2007 3:51 PM, Ashok Madhavan <[EMAIL PROTECTED]> > > wrote: > > > > > i think doing the pagination in the sql is the better way. > > > you can do it using nested selects. > > > > > > the sql for getting the rows between 50 and 100 goes like this : > > > select FIELDNAME, USERID from > > > ( select FIELDNAME, USERID, rownum num > > > from ( select A.FIELDNAME, B.USERID > > > from wdchangelog A, WSUSERS B > > > where A.configUnitID = ? > > > and A.USERUID = B.userUID > > > order by A.FIELDNAME ) a > > > ) b where num between 50 and 100 > > > > > > the above is specific to oracle. but all DBs have equivalent of this. > > > > > > regards > > > ashok > > > > > > On Dec 10, 2007 1:55 PM, Stefano Tranquillini < [EMAIL PROTECTED] > > > > wrote: > > > > > > > Hi, > > > > someone know's how i can have a paginedQuery? > > > > i try to use queryForPaginatedList but is deprecated. > > > > tnx > > > > > > > > -- > > > > Stefano > > > > > > > > > > > > > > > > > > > > -- > > Stefano > > >
