|
Charles
Seems when I started working with case-insensitivity in one of our apps that the CRTxxx settings do not affect SQL processing. But this could just be my memory refusing to work when on vacation.
The thing that is not convenient - the SET OPTION for case-sensitivity cannot be changed on the fly - it is in effect for a given module - and we would have a data area, say, to control whether to use one of the other. It used to be done with the lower and upper functions, and I want to change from that, as discussed here. Maybe the good thing is, it can force the use of modular techniques.
Vern
-------------- Original message -------------- From: "Wilt, Charles" <WiltC@xxxxxxxxxx>
Walden,
You are correct.
However, my personal preference is to use the SET OPTION in the source rather than depending on the next guy to specify the correct options on the CRTSQLxxx commands.
Charles Wilt --
Software Engineer CINTAS Corporation - IT 92B 513.701.1307
wiltc@xxxxxxxxxx
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l- bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich Sent: Thursday, July 31, 2008 2:32 PM To: Midrange Systems Technical Discussion Subject: RE: Case insensitive searching with SQL
For a stored procedure, UDF, or embedded SQL, add the statement SET OPTION SRTSEQ = *LANGIDSHRI believe (not on i right now) that SRTSEQ is also an option on the CRTxxxPGM commands.
Also, IIUIC, older releases of SQE cannot use an index marked that way so you'll be forced down CQE, but I believe that's now resolved (5.4, 6.1, not sure which? I sure Elvis or Birgitta will chime in :-) )
-Walden
--
Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.