Looks like the database was created with a different collation, and contains a few globals with this collation.
I don't remember, but I think in the messages.log it should show which collation is expected. And then, you can change it in Management Portal, and with NLS. When you activate NLS which contains the expected collation, it will be able to mount this database.
This part I can do, but, I don't think we should even consider it. This is part of IRIS SQL Dialect, and it's not good when some SQL queries may not work with different connections, e.g. using JDBC, or SMP.
It looks like there is something wrong with an instance. And It would require some more details, such as the exact version, edition, and the way how it was installed. And just check it manually if HSSYS is present in the system, as well as HSLIB with databases, and all databases are accessible too.
I think it depends on what type of application you have on IRIS.
If it's just some frontend application, then there is a variety of projects to do this task, as it is not much related to IRIS
What exactly do you want to test?
What happened to ARM64 images again?
Creating an Index with SQL, not directly in ObjectScript, will build Index by default if you don't say do not do it.
Well, most probably IRIS there running in a container, and you are looking at the wrong place. Inside the container, from IRIS, there will be /usr/irissys, outside it will be somewhere else
No it's just randomly can output errors, and output just nothing
Nope, plain $system.OBJ.Compile outputs the same way.
It's the compilation log in VSCode, why should I even try this way?
with zpm you can use additional parameter for it
zpm "test module-name -only -D UnitTest.Case=Test.PM.Unit.CLI:TestParser"Use class name only to run all tests there, or add Method name to test only that method in the class
There are no reasons for them to be ClassMethods, UnitTests is quite a complex thing, and it's there are use-cases where it needs to be this way.
VSCode has a way to help with running tests, but it requires implementing from our side
Why would you need XML?
Have not seen such errors, but how defined the mirror members, by hostname or by IP?
well, ok, yeah, I did not notice it. But still, the usage per process is still an important part. And even if the leakage is real, it may happen in ZPM itself. The testing scenario does not look like proof much, installing and uninstalling zpm multiple times does not like a real scenario.
Have a look at what will show this query, the result in KB
echo 'select sum(memorypeak) memorypeak,sum(MemoryUsed) memoryused from %SYS.ProcessQuery' | iris sql irisYou have to look at `/usr/irissys`
I think you forgot about memory per process, which I would say is not limited at all by default anymore. So, your "leaks", may happen in the processes. ZPM is quite a big package, and the installation will use multiple processes.
So, having most of the memory just mostly for buffers does not work for IRIS, while you need room for the processes, and if you would go to production, you have to have in mind how many active users you would expect and decide how much memory they will consume.
You can also use SAM, or plain Grafana for it, which is more suitable for real-time dashboards
And I've recently introduced IRIS support to Apache Superset, which now can be used to show charts on plain SQL tables.
There is no way, to catch the possible issues for the previous version of IRIS.
The best case scenario is if you automate the build process, for instance with Docker, and test a compile stage on different versions of IRIS. But the ability to successfully compile may not prove that it will work, it would be better to have some unit tests, which will check it.
One more thing, may help, to check it, using the such tool as ObjectScript Quality, can help with checking System's API version. Where you can set the oldest supported version of IRIS, and during the scan, it can check if Methods are available in that particular version.
Apache Superset in ideas - https://ideas.intersystems.com/ideas/DPI-I-288
irissqlcli actually has a web version too, but, yeah, it is still a terminal, and not so powerful
Or just add this to the end of docker run command
-a "iris session iris -U%SYS '##class(Security.Users).UnExpireUserPasswords(\"*\")'"
I wanted to implement it as part of irissqlcli, but did not have time yet.
:py for embedded python
.png)
or
irissqlcli iris://_SYSTEM:SYS@localhost:1972/USER < c:\InterSystems\mysqlcode.txtin irissqlcli, you can use \dt or .tables
This may require additional privileges