Re: . RPG and SQL view/index

I'm curious what you mean when you say a VIEW is a 1-time build - a VIEW is a SELECT statement contained in an LF with an SQL type - do DSPFD on a VIEW object.

So a VIEW always runs the SELECT when opened, thus having whatever is the current data - always up to date.

As someone else said, a VIEW doesn't have any sorting, no index, so not as useful in an F-spec, which I think was the OPs request. An index, OTOH, works fine - you can even put, as in your example, selectivity in a WHERE clause, and you can open a subset of columns - this becomes quite a bit like the traditional LFs, although there is much more potentiality using a WHERE clause than in the tests in DDS.

What am I missing?

Cheers
Vern

On 7/7/2021 12:50 PM, Timothy Feldmeier wrote:

I don’t think you want to use a VIEW—views are a 1 time build. I think you want to use am index- the data is always up to date.
To get the outcome of a SETLL and READE- You need to read a cursor with an index.
Index example:
CREATE INDEX statcdtf
ON statcode (code1, code2) <-----over what Table and <-----------------------YOUR KEY ORDER
WHERE APAGENT IN ('A', ‘B’') <---- CONSTRAINT
RCDFMT TFFM
ADD ALL COLUMNS <---------------- TO GET ALL THE COLUMNS IN THE TABLE

The information transmitted is intended only for the person or entity to which it is addressed and may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer.