While WinSQL does not offer direct support for InterSystems products, out of the box, and as far as I know, no plugins exist. I would recommend switching to something with better support, e.g. Datagrip or DBeaver.
Or if it's required using WinSQL, you may write a plugin for it or order it (I can help with it), which will offer better support.
So, actually I have no idea why this file is there, but it's something else, there should be another file like intersystems_irispython-3.2.0-py3-none-any.whl, and it should be installable
I've removed your images, with broken urls, could you update post with an error, you get
and command you use
Any news on when ARM64 images will be published too, again?
VSCode has such feature, from Menu Go -> Go to file, (cmd+P/ctrl+P)
By this name only one platform is available and it's x86, not arm64
When the google group was quite active, years ago, I did some analytics as well, and as I remember, there were quite similar numbers as well. And we had a dedicated Russian forum and had just about 10 active people there.
My suggestion is, that, Developers on InterSystems technologies are not used to using the Internet for their issues. They probably may ask colleagues by company, but not the Internet. As you would see on StackOverflow, there is a huge amount of questions and answers on any language and technology. And even so, we have jokes, that some developers write code by copy-pasting code from StackOverflow. But apparently, it's not the case with ObjectScript and IRIS. And we have just a few questions per year on StackOverflow and only a couple or so people who would answer there.
So, I think, InterSystems developers mostly prefer to solve issues on their own. And this is a main issue as well. Because they may miss some new features that appeared in the technology, some useful projects or technics.
And I'm sure that, any involved developer should be part of spreading the importance of using DC amongst his colleagues and encourage them of using it, at least to read articles.
Yeah, that's really, so. Redis has that feature, so you can set a time to live for the value, and it will disappear after that. In IRIS The only way to have something that will be deleted automatically is, Process-Private Globals, but their time to live is tied to the process, and you would still need to clean up if your process is long living.
What exactly do you want to achieve?
JDBC Drivers are not applications, so, there is nothing to execute, it is supposed to be used by another application, which can work with JDBC drivers.
Yeah, actually, in several projects I've used %CSP.REST to process the whole application. Static web files and REST itself. And the main cause to do so is that the internal webserver did not accept index.html as default index. So, it required to putting it manually to the URL, or using %CSP.REST, which work with static files, and correctly processes index.html. And it requires just one Web Application configured. But in case, when an application is partly anonymous, requires more attention to security.
Debugging uses WebSockets, so, make sure that your web server is configured properly for WebSockets.
Any reasons for doing this? This is not how it is supposed to be. REST should answer with Status 401, and optionally with methods available. And web application when gets 401, it knows that it has to authorize the user, and shows its own page or initiates SSO, depending on the task.
Anyway, if really do this way, It looks like %CSP.REST extends %CSP.Login, and it has Method Login
Called for a REST page in the event of a login being required
Did not test it, but I would expect it will do what requested
Then you can always get the latest version on WRC
So, that's it? No more ARM64 images?
Yeah, with docker it will be easier to offer a working environment
And we already have a lot of open-source projects, based on docker. But switching most of those projects from Community Edition to normal now will require additional configuration, on adding webserver container next to IRIS. And I think we should think already about it, and produce new projects, even on Community Edition, with WebServer as well. So, it will be easily switched for any reason.
Yeah, I would not expect less, from such an experienced man. But, I'm mainly worried about beginners.
Offical Apache, does not offer any builds for Windows, it offers using 5 third-party projects, one of them with a dead link. And even mentioned by offering 4 different builds of the same version. And not everyone can easily decide which version is needed.
You should ask WRC, for the help if you have support
Seriously?
As you can find below, using IIS can be forbidden by company policy. And I totally agree with that.
Installing Apache on Windows, it's quite a trick. Fortunately, I'm not a windows user, but as far as I know, it's not so simple to find Apache on Windows, there are a few different builds of it.
And Installing nginx which will work with IRIS, even requires building it from source code, according to InterSystems Documentation
So, yes. I'm strictly staying with my position. That even installing a webserver may cause pain. And on top of that, if it will require a production-ready configuration, with restricted access, became even trickier.
I mean, a lot of stuff still really depends on a web server. It's quite difficult for a beginner to do anything useful, having bare IRIS, without any web server. SMP is a dependency, Atelier API is a dependency and so on
But it should be a bit more gentle way, first of all, remove any dependencies of this, or make them at least optional.
I think, it may skip Abstract classes, and there are only Abstract classes
Atelier API is just for IDE, it's not supposed to call any custom call.
There is a way, that you could call SQL Proc, via SQL Query. But it is not what I would recommend
Yes, they already mentioned that in another post
But, how knows how long it will last, the later version may remove that support
The fact that it's still available in the Community Edition, does not mean that it will not be removed there too. And I'm sure not all developers, can use Community Edition in development, because, not all features are available in Community Edition, and it's very limited by the size of the database and connections (even after increasing). So, for most of the customers, it's rather impossible. But now, InterSystems I would say forcing to use it in development by any developer. So, I see, no reason of pushing Community Edition as an option for developers. It's a good alternative, but useful for a minor part of the developers.
Using Atelier API, for such task looks a bit strange. Did you look at the documentation about what is available for direct use in .Net?
What do you mean, what do you have by right click?
It will not help anyway. Developers installing instance locally, will have to take care about configuring local web server as well, even just to use VSCode.
.gif)