M:N Relationship is a recurring object of my interest for a long time. So the subject turns up with me repeatedly. For this article, I found a nice example with TWO separate M:N relationships. Some M:N².
It is not pure fiction but taken from a closer view of OEX Contests that we run on a regular base.
This package offers a utility to export an XLarge Global into a JSON object file and to show or import it again. In a previous example, this all was processed in memory. But if this is a large Global you may either experience <MAXSTRING> or an <STORE> error if the generated JSON structure exceeds available memory.
This example demonstrates the difference you may experience when you write to Gllobals directly from Embedded Python compared to native ObjectScript.
To make this demo useful I start 2 background jobs that simply write sequentially to a dedicated global. A common control method signals for a synchronous start. Similar a common stop & view interrupts data feeding.
You may have seen my series of articles on GlobalToJSON closing with Embedded Python. And to me, Embedded means inside a Class and not PEX or other external variants. The first variants showed that ePy is not an ultimate requirement. ISOS/COS may do it as well. Here I try to position ePy inside IRIS.
In my article I described the work using iris.gref . As the official documetation is rather slim on the subject it was necessary to dig into it. Using the power of Python I was able to detect what I needed but was hidden. I decided to share this with you. pydoc did the magic.
I will give you some additional information on my first embedded Python package. it is written as a mix of python and ObjectScript to take the best of both worlds.