RE: XMLSERVICE and losing Wildcard from SQL LIKE

OK, through some debugging I have the issue narrowed down to the percent sign getting posted correctly as %6C and then getting converted somehow to %25 in XMLCGI.

I saw an old post from Aaron on this, but I'm not sure if that's relevant since the %6C is present in the input buffer.

Just gets turned magically to a space along the way.

Aaron pointed me to CGIConvMode setting but that doesn't seem to be helping so far.

Any additional insight appreciated.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

-----Original Message-----
From: Richard Schoen
Sent: Wednesday, December 16, 2015 8:07 AM
To: 'midrange-l@xxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxx>
Subject: XMLSERVICE and losing Wildcard from SQL LIKE

Changing the topic title........

Well, setting the *cdata control option solved the issue reading data. Data gets CDATA encoded automatically. Nice.

Now I ran into another one which seems pretty basic.

The following SQL query works:

select * from qiws/qcustcdt where lstnam like 'Henning'

When using a wildcard with a LIKE statement, XMLCGI seems to drop the pct sign %

select * from qiws/qcustcdt where lstnam like 'Hen%'

I have tried the request both encoded and decoded and it appears the percent sign from the query string always gets dropped.

You can see below that the XML response shows the pct sign was dropped from the wildcard.

<prepare conn='myconn' stmt='stmt1'>
<success> +++ success select * from qiws/qcustcdt where lstnam like 'Hen' </success>
</prepare>

I wasn't sure exactly where in the source to look for debugging this issue, but was curious if anyone else has run into the wildcard LIKE issue with XMLSERVICE/XMLCGI.

I was going to check to see where the percent gets stripped off and possibly code a workaround. (No, don't make me do it !!)

This seems pretty basic so either I'm confused or there is a basic flaw when using wildcard SQL.

Any thoughts appreciated.

I would really love to be able to recommend using XMLSERVICE for production use, but still not there yet.

Thanks.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on: Twitter | LinkedIn

-----Original Message-----
From: Richard Schoen
Sent: Tuesday, December 15, 2015 8:40 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: XMLSERVICE and Parsing XML Responses

I'll report back after I test Aaron's tip.

I know I can modify XMLSERVICE as well as other open source, but since XMLSERVICE is being widely deployed and even as part of OS updates that would not be my first choice which is why I posted here.

I figured it was some of my XML ignorance causing me issues :-)

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on: Twitter | LinkedIn