Reading JSON with SQL on IBM i
A field holding JSON can be read with SQL. Four levels, from the first JSON_VALUE query to the cases where a value quietly comes out NULL.
A field holding JSON can be read with SQL. Four levels, from the first JSON_VALUE query to the cases where a value quietly comes out NULL.
FTP, ODBC and data transfer reach the database without going through menus. The two SQL views for checking who controls that access.
QCRTAUT defaults to *CHANGE, so public authority is wider than anyone decided. How to measure it with SQL before restricting it.
QAUDJRN is not on by default and cannot be enabled retroactively. The command to turn it on, the functions to query it, and the library they live in.
No revolution, but three or four things that take manual work off whoever administers the system. And one that concerns anybody sending mail from it.
Calling an external API from an RPG program needs no extra software and no rewrite: it can be done in SQL, in a few lines. The available routes, and when each one makes sense.
When a query slows down, the cause is almost always a missing index or a condition written in a way the database cannot use. Here is how to find out instead of guessing.
How software is written, compiled and maintained on IBM i: sources, ILE, RPG, CL, DDS and SQL, debugging and modernisation, with IBM sources.
How to write SQL inside RPG, why SQLCODE zero does not mean everything went well, and where injection hides on this platform too.