Re: Problem with an SQL View that has selects/omits

["James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>]

Mark S. Waterbury wrote:
> You do know that an SQL VIEW does not include any index automatically, 
> right?

Right, and if there's a process for attaching an index to an SQL VIEW, 
so that RLA can access it by key, I don't see it, and if I knew about 
it, I don't remember it. (There certainly OUGHT to be one, if there isn't!)

One difference: when I check the number of records, the DDS LF returns 
the number of records in the PF (10, for the "guinea pig" library I was 
given), while the SQL VIEW returns the number that the WHERE clause 
finds (only 1).

But other than that, I just ran a trace of everything that goes on 
between returning from the SETLL-equivalent call, and issuing the 
READ-equivalent call, and in some 150-odd instructions, the only 
difference is an extra iteration of a loop that massages the 
aforementioned total number of records, so it can be displayed.

I'm now going to do something in RPG (thanks, Chuck), that will 
hopefully simulate the point-of-failure, to see what *it* does.

--
JHHL