RE: Re[2]: Question using jdbc/jt400

From: Carl

On 8/30/07, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

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.

This does not directly address my earlier response which you quoted,
and I maintain that if you find yourself seeking outside the bounds of
your ResultSet, you have either selected the wrong resultSet or your
bounds checking needs work.

Actually, it does address this specific issue. You just aren't seeing it.
Let's take the simplest of functions, the customer lookup. A user begins a
lookup by getting a list of records in order. They key in the first few
letters of the name and ask the list to be repositioned. This is a
SETLL/READ. However, they realize that they are actually just PAST the name
they wanted, so they do a page backward.

THIS CANNOT BE DONE IN SQL WITHOUT TWO SEPARATE RESULT SETS. Just can't be
done, because YOU CAN'T POSITION BY KEY. It amazes me how this simple
capability is still not even in the newest SQL ANSI recommendations.

Until you understand this fundamental lack in SQL, it's really not worth
discussing. (And on a personal note, phrases such as "your bounds checking
needs work" which both miss the point of the problem AND make a backhanded
insult to my programming skills disincent me to continue the discussion.
But maybe I'm just a thin-skinned wussie.)

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.

This statement clearly demonstrates to me that you did not understand
the point I was attempting to make, which is that record level random
access may not be needed. I'd be interested in a high level
description of a situation where it is. My question is why you would
need to "postion by key" rather than fetch the records you want and
get to work on them?

The basic model is the "work with" display, used in probably every business
application written for the iSeries since 1980.

Joe