Re: Question and suggestion regarding rownum

What are you developing the application with? I've got a PL/SQL Web Toolkit presentation that describes a technique using hidden HTML form fields to store either primary keys or rowids for the query result, then using these to maintain page context. Other options would be to store the context in an database table, but you'd have to develop appropriate logic to time-out entries and clean them out (delete them) as appropriate.

The hidden HTML form fields solution has the advantage of maintaining set consistency and avoids needing to reselect rows that are not displayed, but has the disadvantages that a key from for all rows of a large resultset must be returned before the user can see the first page, and all keys must be passed to and from the browser for each paging operation.

The option of storing context (pks or rowids) in database table would improve performance, and the code to clear out the table would not be too complex.

-- 
Mark C. Stock
email mcstock -> enquery(dot)com
www.enquery.com
(888) 512-2048


<ketansweta_at_sbcglobal.net> wrote in message
news:THFsb.30024$FD7.22223_at_newssvr27.news.prodigy.com...


> Hi! Folks

>

> I am sure many of you have come across this problem which I am facing and

> hope to have some suggestions.

> We have an web application with tones of where clauses and group by but

> eventually the result set could be any where

> from 1 to 10000. Now the web page would display only 1 to 10 items after

> which if you would click on next it would show

> from 11 to 20 - till here it is some what do able - the problem lies when

> the user click on directly 45th page which should show records

> from 2000 onwards. I was thinking of using the rownum function .. remember

> this is a select from a 500K table - .

>

> Any folks who have a better idea or suggestion would be great ful.

>

> Thanks

> Ketan

>

>