All
Accepted answers
Dmitry Maslennikov · Feb 19 go to post

A bit hackish way

{
  while IFS= read -r line; doecho'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
Dmitry Maslennikov · Jan 31 go to post

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

Dmitry Maslennikov · Jan 23 go to post

This is how COPY/rm  look like in reality

FROM containers.intersystems.com/intersystems/iris:latest-em

COPY iris.key /usr/irissys/mgr/iris.key
RUN rm -f /usr/irissys/mgr/iris.key

using dive tool, to inspect docker images

The layer with iris.key is still there, and adds some space into final image

Dmitry Maslennikov · Jan 23 go to post

important note

When you add something and delete during build with Dockerfile, you should remember how docker build works, and do it in one RUN line, if you do COPY/ADD file then delete it in RUN, it will not delete file from the image, it will hide it in the final image. Due to layered nature of Docker images, COPY/ADD/RUN are separated layers, and generates a difference between. So, file still can be exctrated. 

And nowdays, the best approach to using binding in RUN

....

RUN \
  --mount=type=bind,src=.,dst=/opt/app \
  cp /opt/app/iris.key /usr/irissys/mgr/iris.key && \
  iris start IRIS && \
  ....
  iris stop IRIS quietly && \
  rm -f /usr/irissys/mgr/iris.key

or you can mount it straight to the way where it's expected, and it will not stay in the final image

...

RUN --mount=type=bind,src=/iris.key,dst=/usr/irissys/mgr/iris.key \
    iris start IRIS && \
    /bin/echo -e 'do ##class(%SYSTEM.License).CKEY() halt' | iris session IRIS -U %SYS && \
    iris stop IRIS quietly
Dmitry Maslennikov · Jan 6 go to post

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.

Dmitry Maslennikov · Dec 22, 2025 go to post

Yes, in some cases this works, and even got quite fast fix, thanks.

I hope, we can get more fixes done and not only with SQL

Dmitry Maslennikov · Dec 22, 2025 go to post

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.

Dmitry Maslennikov · Dec 10, 2025 go to post

Now, how wonderful would be, if InterSystems produced official product like this, and Community Edition would get much higher number of connections available there, when nothing needed only for Enterprise is left there.

Dmitry Maslennikov · Dec 10, 2025 go to post

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?

Dmitry Maslennikov · Dec 9, 2025 go to post

Most of the time it generates queries that make no sense. But still supposed to be working.

CREATETABLE t0(c0 BIT );
SELECT * FROM t0 WHERE (c0 IN (c0, c0, c0, c0));

Gives

SQL Error [400] [S1000]: [SQLCODE: <-400>:<Fatal error occurred>]
[Location: <Prepare>]
[%msg: <<UNDEFINED>in+4^%qaqpnl *mt("v","4")>]

https://ideas.intersystems.com/ideas/DPI-I-881 

Dmitry Maslennikov · Dec 8, 2025 go to post

Yeah, I know that it's works without those brackets. But the thing is that SQLancer generates SQL queries randomly, and expected to produce queries that looks ridiculous, but syntactically correct and expected to work

On community edition due to small amount of licensed connections, and issue with fast releasing available connections, and probably due to too many failures on the network layer in the communication it's very fast start to fail to connect due to license limit.

Dmitry Maslennikov · Dec 1, 2025 go to post

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")
Dmitry Maslennikov · Nov 27, 2025 go to post

It does not look like that my implementation will be even approved for the contest.

I may need to find a better idea to implement for the contest, while it's extended

Dmitry Maslennikov · Nov 26, 2025 go to post

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

Dmitry Maslennikov · Nov 20, 2025 go to post

it fails on 2024.1 

USER>s json=[{"s":"iPhone1"},{"s":"iPhone2"},{"s":"IPHONE3"},{"s":"IPHONE4"},{"s":"Phone5"}] 

USER>d ##class(%ASQ.SetUtils).pp(json.apply("$[*]?(@.s like_regex '\p{LL}\w+')")) 

<THROW>parse+8^%ASQ.Parser.1 *%Exception.StatusException ERROR #30000: ASQ SYNTAX: Error in expression, found 'string '\p{LL}\w+'', expected ')'

USER 4e1>w $zv
IRIS for UNIX (Ubuntu Server LTS for ARM64 Containers) 2024.1 (Build 267_2_23660U) Wed Aug 28 2024 15:23:37 EDT
Dmitry Maslennikov · Nov 20, 2025 go to post

Finally there is something, but that's still look like way less then it actually supports

There should be `like_regex` predicate, which would help with case insensitive search, but I did not manage to get it working. Looks like it partially implemented, at least on the version 2024.1 I'm using

Dmitry Maslennikov · Nov 20, 2025 go to post

Thanks, I've asked for this for the last 10 years at least.

I thought there was supposed to be a very different driver for NodeJS, with SQL support, driver published I don't know what for, and who will use it without access to SQL.

Python driver, I would not say the best implementation, I tried to report about issues there, and were told that's not going to be fixed.

Dmitry Maslennikov · Nov 19, 2025 go to post

Is ASQ or JSON Path in IRIS already documented or not?

I can't find anything in the documentation

And I tried to play with JSONPath online, and I can't figure out why InterSystems ASQ, does not understand at all what perfectly works there. So, is ASQ is a superset of JSONPath or just fully different implementation?

How to test it? It just always complains, and with no documentation quite difficult to understand what's going on, and how to fix it