Re: Converting Case with a Varying Field

Hi Mike

You might look at using a LANGIDSHR index on the data, if possible - then it's read without regard to case. The order could be more like ASCII in my experience, however.

I think this is possible just with regular RPG stuff - I've done it with SQL, setting those in a SET statement early in the module.

But it's worth testing against using that UPPER function in a SELECT statement.

HTH
Vern

On 8/20/2012 4:38 PM, Michael Naughton wrote:

Not 100 million, but potentially several thousand while the user is waiting for their screen to come back. (I'm implementing an "ignore case" option for an app where the user types in a string and then gets a list of all records that contain that string
"anywhere". There may be several thousand records in the main database, plus each record may have more in associated databases -- notes, etc. -- so there's likely to be a dozen or more searches per main record. But maybe that's nothing to the i? :-)


RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx> writes:

Not necessarily - are you doing this over 100 million records? Or
onesy-twosy?

The real code just sets a host variable going in, calls a program to
convert it, then sets the host variable back again - nothing much. The
stuff we'd write could easily be more complex than is done in the called
SQL program.

HTH
Vern

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.