Re: New SQL HTTP_POST question -- MIDRANGE-L

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

Subject: Re: New SQL HTTP_POST question
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 14 Jan 2022 08:39:37 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Trying to play with your example in iACS I got "the literal exceeded the
maximum line length 132".
Dunno if that's the iACS SQL window complaining or Db2.
So wild guess with no real evidence: Break up your JSON into multiple
variables and use Db2 CONCAT() to join them inside the HTTP_POST function
call.

On Fri, Jan 14, 2022 at 8:27 AM Bobby Adams <bobby_adams@xxxxxxx> wrote:

It is not a public sandbox. I appreciate your willingness to help.

Is there a way I can see what SQL is sending to the API? Would I have
to do a line trace?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: New SQL HTTP_POST question , Bobby Adams

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.