×
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.
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
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
