By any chance, does your table have an identity column? If so, you
can note the identity value of the last record on the page, then do
all subsequent selects where > or < the ID. We've started doing that
in tables we create. But for existing tables (the bulk of our
database), we use Charles' suggestion.

Mike E.

On Tue, Aug 12, 2008 at 4:18 PM, Coyle, Stephen F. <SCoyle@xxxxxxxxxxxxx> wrote:
Hi All,
I have a web service that calls a SQLRPGLE program and returns a
maximum of 1000 records. If a statement selects over 1000 records, and
multiple calls to the service are needed, how will the service know
where the current cursor should be?
The .net consultant who is writing the front end wants to pass a
page number, so for records 1000 through 2000 he would request page 2.
I think this would be possible using FETCH RELATIVE but I think this
would require that the cursor cannot move between calls and I cannot
guarantee that. Correct?
Just wondering how others might be handling this paging
situation in a web service.

Thanks for all suggestions and ideas...

Currently I'm using "Fetch C1 for :MaxElem Rows Into :OutDATA ; ".

- Steve
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].