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



On 10/14/2016 10:51 AM, Sue Romano wrote:
I can explain this one. All SQL names can be up to 128 long when
delimiters are removed. For any " in a name, the delimited form of
the name must have that character doubled. So you could have a name
with 128 " characters. To use that name in an SQL statement, you
would need to double each of the " and then add delimiters on the
outside - for a total of 258 " characters.

OK, I _think_ I understand what you are saying here.

A name like this: a3 xyz "test double quote"

Would have to be added using the following command:
ADDPFTRG FILE(*LIBL/F0) TRGTIME(*AFTER) TRGEVENT(*UPDATE)
PGM(DEVDMGWRK/A1) TRG('"a3 xyz ""test double quote"""') TRGLIB(*FILE)
ALWREPCHG(*NO) THDSAFE(*UNKNOWN) MLTTHDACN(*SYSVAL) TRGUPDCND(*ALWAYS)

The embedded double quotes have to be duplicated.

Correct?

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.