From: Carl

Then I would wonder if that ResultSet is the set of results you actually
needed?

It is if the user is doing the most fundamental of funcitons: paging through
a list of records by key and positioning the list.

Perhaps I was really wondering whether the RPG idiom of SETGT/READP is
even
necessary when using sql, since you can determine the sort order and
collect a result set with the records you actually want in one request,
not two. For example, given a table with a key of a single integer, with
records
1-5, where you wish to read record 4 through 1, in RPG you might write:

Unfortunately, SQL still has no capability to position by key within a
result set. Instead, you must recreate the result set every time. This
fundamental issue has been discussed on this list and on the RPG list (where
it really belongs) many times.


There is no need to even move backwards in the result set.

The issue is when the user positions themselves in the file and then page
backwards. There simply is no way to do this in SQL without rebuilding the
result set.


It's the fastest way to get the last record in a set without having to
have
indexes in both directions.

Surely if written in RPG, but when writing code in java and using JTOpen
record level access, is the process of requesting a record then
reading the previous (emulating SETGT/READP) faster than issuing a
single sql statement?

Yes.

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2022 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.