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 EDTFinally 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
.png)
.
IRIS License Agreement is a major obstacle on developing bigger integrations like Golang, when InterSystems may conseder such projects as violation for no reason. And the whole community driven ecosystem's future could have issues
Golang is just a start, I hope to see much more libraries in the future, and it's difficult to rely solely on InterSystems with this question. I'd like to publish my Rust work too.
.png)
So, bugreports not visible to other users?
Ideas portal originally public, and would mean bug reports mostly related to projects to open source, or non enterprise.
If bug reports will not be open to everyone, means that InterSystems would have no intention to resolve those bugs, for issues with no support. And possibility to have duplications, which will not help. Closed bug reports will not get any votes, and it will not help to prioritize such issues.
What's the point then? While it's closed I don't see any point to post any more issue, it will not be resolved anyway.
faced that issue too, reloaded page and it's appeared
ahh, yes, I'll try to have a look
with so many projects on my hands quite easy to get distracted, and since it's an open-source project not easy to find a time to properly maintain them
could you try iterm, how is it working?
https://openexchange.intersystems.com/package/iterm
Thanks, finally, the place to report issues discovered during open-source projects development .png)
I love the challenge of bringing IRIS into new technical worlds. So far I've built tools and integrations for Go, Python, Node.js, and Java, and I'm eager to continue exploring areas where IRIS hasn’t stepped yet. Creating these “first steps” is what inspires me professionally.
Aside already mentioned above. This implementation does not work with SQL in IRIS, it was made to work the same for IRIS and for YottaDB and co.
But in most cases what's needed for new developers is SQL
What I did is just copied the logic from Python to Go, nothing else. It does not require reverse engineering, because it's written in pure python. I did not decompile anything.
Nothing is actually close, undocumented yes. Anyone can read that code and repeat what I did.
That's great to hear, I hope we can resolve this soon.
Thanks
Still support, for sure, contact me directly, i.can help with implementing it.
I closed it. My contest app was removed for no reason, even after I won, so there's no reason to keep it open.
Looks like ML edition is deprecated.
InterSystems removed them everywhere.png)
Even for Enterprise most recent version is 2024.1.png)
Well, it's mostly like looking at the open implementations, for instance InterSystems Driver, packed as Python package as zip archive here https://github.com/intersystems-community/iris-driver-distribution/tree…. It contains the whole protocol implementation.
Some parts of protocol even in plain in IRIS classes too.
Right
It does not use any already published, it adds a new one for Go, works directly with port 1972
That's a great work, but today we have containers, why do not use containers?
For the go project, I have 3 articles
I'm quite new to go world, let me know which package exactly you talking about, I'll have a look