well, too many things to consider when move from any much more popular RDB, to IRIS.

• first of all, most of such applications already uses some popular external programming language. when moving to IRIS, team would need to learn ObjectScript, and rewrite entire application from scratch. it will be mission impossible to to just easily switch application from using from MSSQL fro IRIS, cause MSSQL much wider supported, when IRIS not supported at all, except some community support which anyway is highly disapproved by official InterSystems.
• IRIS SQL is very outdated, any move from some modern database would mean moving back in 20 years. And will require to remove most of the modern SQL features from the application.
• even if you decide to write your own driver to iris that will be working with migrating application that will be considered as license violation.

You should raise this issue with IPM team, there are some work related to python, where it happens, and it could be related to intersystems-irispython official driver, which tend to fail randomly with segmentation fault, and this error most probably is comming from Python

A bit hackish way

{
  while IFS= read -r line; do
    echo 'write *27,"[1F",$namespace,">", "'$(echo $line | sed "s/\"/\"\"/g" )'",*27,"[1F"'
    printf '%s\n' "$line"
  done
} <<'EOF' | iris session iris
write $zv
write !,"hello ", $username,!
zn "%sys"
halt
EOF

and output

$ bash test.sh 

Node: e91a00f6512e, Instance: IRIS

USER>write $zv
IRIS for UNIX (Ubuntu Server LTS for ARM64 Containers) 2026.1.0L (Build 193U) Tue Jan 6 2026 01:46:47 EST
USER>write !,"hello ", $username,!

hello irisowner

USER>zn "%sys"

%SYS>halt

Hi! I’m in for a random coffee chat ☕
Location: Australia, Melbourne
Availability: Mon–Fri, 11:00–16:00
Happy to chat

I've updated the building process. Now should get updates at least in one day after official release.

And returned ML version, even when there is no official build.

I would not say that I did not expect that.

I provided all source code, which easily shows errors, but as an answer got 

we can't reproduce this bug

If I could resolve those issues by myself I would do it, but this is InterSystems responsibility 

With those errors, I would not use JDBC in production, would not even try any project, due to the bugs I discovered with SQLancer project.

And for Python, luckily I already have driver in pure Python that works much more stable than new official one, so, would use it, and would not use official driver, as I see that it can fail at any time. 

I have no reason to use WRC for reporting these bugs, as I did not find it for the company, I found it in open source projects. And after discoveries, would not even try implementing it in company, so, no point.

Thanks, and congrats to others winners

#4

Have a look at VSCode, Studio already reached end of life, no reason to keep using it.

Why not to put which standard exactly it exactly?

It says, see the documentation for more information. Where it is? The only found page have not been changes for a few versions.

Where is JSON_VALUE, JSON_QUERY, JSON_EXISTS that defined in the standard?

Happy Birthday DC

I saw you used mine sqlalchemy-iris, looks like implementation is much easier this way, thanks.

WebTerminal not a terminal in that terms, it's a just an emulation, you need to use real terminal.

InterSystems now publishes driver to the maven central repository, so instead of github repo, should be used this for maven

<dependency>
    <groupId>com.intersystems</groupId>
    <artifactId>intersystems-jdbc</artifactId>
    <version>3.10.5</version>
</dependency>

or in gradle

implementation("com.intersystems:intersystems-jdbc:3.10.5")

Are you sure that you use it correctly, do you have a much closer example that will show that behaviour?