× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Another advantage of sorting the data that are already displayed
is letting the user sort the SFL by the column the cursor is on
We have (a few admittedly) programs where the user points (moves the
cursor) to
a SFL column and hit F16 (ascending) or F17 (descending) to sort the data.
like
SORTA %SubArr(SFLDATA(*).HDDATE:1:%ELEM(SFLDATA))

Gad





date: Mon, 10 Oct 2022 11:28:42 -0400
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: Repeated CLOSE and OPEN of SQL cursors

Not an answer to your question as such - but this is why I never re-issue
an SQL statement just to get a different ORDER BY.

My approach is that the initial SQL loads a DS array and the subfile is
populated from that.

If required the DS is then sorted (qsort of SORTA) and redisplayed.

Reason is my belief (and personal experience) that when a user says "sort
the data this way" they mean the data they are _looking_ at. If there is
any chance that the table has changed in the interim period they can get
very confused.


Jon P

On Oct 10, 2022, at 9:26 AM, Alan Cassidy <cfuture@xxxxxxxxxxx> wrote:

I have one last thing stumping me for now to finish a major code change
to boost performance in one program I'm working on, relating to SQL cursors.

The RPG program opens an SQL cursor and the entire subfile is input.
Then the user requests a different "ORDER BY" than the default. I use the
same SQL for the sort, the whole thing is identical except for tacking on
the different ORDER BY clause at the end of the dynamically constructed SQL
statement.

At the top of the subroutine that does the cursor open, the code first
does an Exec SQL Close M1, where M1 is the cursor. Then re-open. So if this
is the second or third time, etc., opening the cursor, the code first runs
the line "exec SQL Close M1".

The issue is that the sorted open is getting sometimes around two or
three times (it varies) as many rows returned as the first open.

Can someone point me to why or how that could happen?

--Alan Cassidy



--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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