I was struggling with a procedure that was meant to receive a string and use it as a filter, I've found that since I want the procedure to do some data transformation and return a dataset, I needed to use objectScript language.
I've created the procedure using the SQL GUI in the portal, and everything works fine when calling the procedure from the SQL GUI but not through a JDBC connection here is the call "call spPatientOS('2024-04-07T12:35:32Z')"
FOREIGN TABLES is a rather fresh feature in IRIS (2023.?) So I was motivated to try something new by own hands. Documentation of Foreign Table from File is a good starting point. Also the related promotional video is fine to start with.
Building my tech. example provided me with a bunch of findings htt I want to share. The first vectors I touched appeared with text analysis and more than 200 dimensions. I have to confess that I feel well with Einstein's 4 dimensional world. 7 to 15 dimensions populating the String Theory are somewhat across the border. But 200 and more is definitely far beyond my mathematical horizon.
The basic idea is to use Vectors in the mathematical sense. I used geographic coordinates. These are of course only 2-dimensional but much easier to follow as vectors in text analysis with >200 dimensions.
The InterSystems IRIS has a series of facilitators to capture, persist, interoperate, and generate analytical information from data in XML format. This article will demonstrate how to do the following:
Capture XML (via a file in our example);
Process the data captured in interoperability;
Persist XML in persistent entities/tables;
Create analytical views for the captured XML data.
Capture XML data
The InterSystems IRIS has many built-in adapters to capture data, including the next ones:
Month
Open Exchange app