Chuck,

An advantage in using an ID Col would be that with RRN() you could lose some records if your file has been created with REUSEDLT(*YES), as a new record could be inserted in an old RRN. ID Columns (AFAIK) would not have that issue.

Regards,

Luis Rodriguez

IBM Certified Systems Expert
eServer i5 iSeries Technical Solutions


--- On Wed, 8/13/08, rpg400-l-request@xxxxxxxxxxxx <rpg400-l-request@xxxxxxxxxxxx> wrote:
------------------------------

message: 7
date: Wed, 13 Aug 2008 12:23:45 -0500
from: CRPence <>
subject: Re: Returning Record Sets from SQLRPGLE Web
Services

So the solution for a case where IDcol is not the first
key, is
achieved by the *or* tests that were added in the example
you gave,
beyond adding the selection of IDcol>savedIDcol to get
the /next page/
of data; i.e. the query requires the additional selection
with OR logic
against each of the other keys. That is what I would
expect. I had
mistakenly thought the post about adding an identity column
was implying
that somehow the IDcol could by itself solve the paging
problem, but
that would only be true for otherwise unordered sets.

FWiW: If that was explained in the link given in an
earlier post in
this thread, I would not know, as the link was to _pay
content_ [best I
can tell, from my results in visiting the link].

I wonder though, what would all of the overhead of an
IDcol achieve
that a RRN() could not, for the same scenario? The
relative row number
is a similarly arbitrary value, as compared to an identity.

Regards, Chuck

Walden H. Leverich wrote:





This thread ...


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].