× 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.



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 08/31/2016 10:42:00
AM:
----- Message from John Yeung <gallium.arsenide@xxxxxxxxx> on Wed,
31 Aug 2016 10:41:44 -0400 -----

To:

"RPG programming on the IBM i (AS/400 and iSeries)"
<rpg400-l@xxxxxxxxxxxx>

Subject:

Re: SQL Where In

On Wed, Aug 31, 2016 at 10:31 AM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx> wrote:
No matter how he does this, he has to change the "array" variable into
a
list with apostrophes around each value, commas between, and
parentheses
around the list.

Why can't he use the "big character string" approach with POSSTR or
LOCATE as Glenn suggested?

(And please note that I'm not asking why it's not the *best* way; I'm
merely asking why it's not *a* way.)

John Y.

It could be "a" way, but you would have to be careful how your "big
character string" is formatted. It might not work because POSSTR and
LOCATE will find the position of any occurrence of a string, not
necessarily the key value for which you're looking.

e.g.:

If you're searching the following string of three character values

'ABCDEFGHI' i.e., values of 'ABC','DEF', and 'GHI'

If you test for 'CDE', POSSTR and/or LOCATE will say it's there and it
is--in position 3. But it isn't really one of the values you intended. Now
if your "big character string" is delimited (using any delimiter--it
doesn't really matter what) it would work. e.g., 'ABC,DEF|GHI'.

Michael Quigley
Computer Services
The Way International
www.TheWay.org

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.