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")

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

Still don't see any issues with $select, that look like Analyzer issue

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

Microsoft is not even against publishing drivers in open source

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

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

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.

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

I did say nothing about critical bugs, critical bugs should go to WRC 

Something that would bother open source developer, some obstacles that prevents to make open source project function in full power, that's where we need public bug reports

No one is expecting that this way is replacing WRC. It's expected that WRC is keep everything private for everyone safety. When it comes to Ideas portal, originally all ideas was public and when Bug reports added there, would think about public too. And anyway ideas portal for bug reports would mean only open source projects where no sensitive data expected, and you could provide a note about it.

Such issues reported through Ideas portal, could be considered as known issues. And may be able to provide workarounds, if InterSystems would not fix it.

Unfortunately after so many years of interaction with InterSystems I can say, if someone without support will report about issues with InterSystems products, those issue will be forgotten. WRC quite fast responses, you are not on support. And I stopped using any form of private reporting. Only public exposure can help in resolving issues. Even projects such as InterSystems Cloud, where a bit different a way of support, it's quite difficult to get support.

As I expected no one gonna resolve bugs reported there, InterSystems is very busy on taking over my projects
I've already implented it a while back and faced bugs in the Driver, I'm asking to solve
Project that I implemented 3 years ago, and did not have any big issues, except that due to issues in IRIS SQL, now somehow does not suit InterSystems
But now InterSystems has decided to make its own SQLAlchemy, I wonder how they are going to do it without solving driver issues