SQL JSON_TABLE using CLOB_FILE limitations -- RPG400-L

Subject: SQL JSON_TABLE using CLOB_FILE limitations
From: smith5646midrange@xxxxxxxxx
Date: Fri, 6 Nov 2020 16:42:40 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

I am playing with the SQL JSON_TABLE using a CLOB_FILE for input. I wanted
to see what it was capable of and I think I have brought this little machine
to its knees. However, it hasn't blown up so maybe that's good news.

Does anyone know if/what limitations there are for this function such as

1. Maximum size for the IFS file to be processed?
2. Maximum number of entries in the table?
3. Maximum number of elements per entry?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL JSON_TABLE using CLOB_FILE limitations , Birgitta Hauser

This mailing list archive is Copyright 1997-2025 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.