×
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.
Never mind. I'm just going to have the stored procedure run a SQL cursor, so the IWS REST API transforms the results to JSON correctly.
A while back I got slightly better performance by using JSON functions to select directly into a stored procedure INOUT parameter (as opposed to using a SQL cursor). I was trying to have my IWS REST API procedure call a stored procedure that used JSON functions to directly select into an INOUT parameter. It gave me the escape characters in the JSON string.
My project can deal with the performance of an IWS REST API procedure that calls a stored procedure using a SQL cursor. So I'm cutting my losses and going with the SQL cursor approach.
Thanks,
Kelly Cookson
Senior Software Engineer II
Dot Foods, Inc.
1-217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com>
From: Kelly Cookson
Sent: Sunday, March 7, 2021 2:42 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: How to eliminate escape characters from JSON in IWS REST API?
How do I get rid of escape characters in JSON output when calling a stored procedure from an IWS REST API?
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.
midrange.com
