Re: Validating JSON Data in a Host Variable -- RPG400-L

Subject: Re: Validating JSON Data in a Host Variable
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Fri, 2 Feb 2018 17:29:36 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 2/2/2018 5:04 PM, Mike Jones wrote:

So, it sounds like the SQL engine is implementing that particular VALUES
request as a SELECT statement in the plumbing.

I myself contend against the SQL vocabulary in vain, but it seems to me
that VALUES is an explicit part of SELECT. Here's how I read the
documentation:

Start at 'select-statement':
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/db2/rbafzintsel.htm

Move to 'fullselect':
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/db2/rbafzmark.htm

There's the 'values-clause' right at the top of the diagram.

The examples of 'fullselect' show VALUES in Example 7.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/db2/rbafzfullselectex.htm

I'll be the first to admit that I get dizzy in these documents, but I
think I got this right.

As an Amazon Associate we earn from qualifying purchases.

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.