the-json-expedition

The last few posts in this series covered adding entries to a JSON array named mrns using SQL and PLSQL. It even handled cases where the mrns array did not exist yet. But what if it did exist but it was not an array? JSON storage is quite flexible we have to gird our code … Read more

The previous post created a procedure to add an entry to a JSON array. This is comparable to the RDBMS situation where no child records exist yet. But (…there is always a but…) for RDBMS the code is exactly the same for first records and all subsequent ones. The JSON code, however requires some adaptation … Read more

The previous post in this series satisfied the following requirement in RDBMS data. Create a new record in a child table that is related to the parent table via a Foreign Key (FK) to a Primary Key (PK) in the parent table. Its much simpler to describe in terms of JSON data: Add a new … Read more

This post explains how a child record is added for a parent record. These terms (parent and child record) are part of the Relational Database Management System (RDBMS) nomenclature. The fully expanded description would be: Create a new record in a child table that is related to the parent table via a Foreign Key (FK) … Read more

Unique Array Values The previous post in this series demonstrated maintaining unique scalar values in JSON data and Relational Data. In both cases uniqueness can be maintained with unique indexes. That sameness does not hold for array as this post will demonstrate. This all comes about due to a new requirement for our patient tracking … Read more

The next feature for the API’s is maintaining unique patient names. This is best done in the database because it is the lowest level of interaction (and defense) for the application. In our case two unique indexes are required – one for the JSON data and one for the relational data: The patient_name column in … Read more