I have a background in electrical engineering ad have been active as software engineer and architect for the past 35 years. Since 2010 I am active in healthcare interoperability, for VitalHealth and Philips. In June 2022 I joined InterSystems.
Hi @PaulSomebody, those are a lot of questions :) I am happy to help when needed.
What country / timezone are you in? I am in Europe/Amsterdam timezone.
Let me know what is a suitable time for you.
Hi @Enrico Parisi ,
I did have warnings from the objectscriptQuality for VSCode plugin on the embedded SQL for side effects but now I re-check that warning no longer seems to be there.
I never liked the different behavior of embedded sql, like when you have no result, you have no easy way to find that out. More importantly, when you have multiple rows as result, you need to start using a cursor and the code becomes complicated.
With ##class(%SQL.Statement).%ExecDirect(), the code is identical whether there is one or there are many results and that way maintainability is better.
But as @Benjamin De Boe already said: It is probably more of a style preference.







executing
docker inspect --format '{{ index .Config.Labels "com.intersystems.platform-version"}}' containers.intersystems.com/intersystems/iris:2025.1
in Powershell fails with error
template parsing error: template: :1: function "com" not defined
This worked for me in Powershell:
$json = docker inspect containers.intersystems.com/intersystems/iris:2025.1 | ConvertFrom-Json
echo $json.Config.Labels."com.intersystems.platform-version"
2025.1.2.374.0
Or alternatively, go to bash first:
docker inspect --format '{{index .Config.Labels "com.intersystems.platform-version"}}' containers.intersystems.com/intersystems/iris:2025.1
2025.1.2.374.0