InterSystems IRIS 2019.1 has been out for a while and I would like to cover some enhancements for handling JSON which might have gone unnoticed. Dealing with JSON as a serialization format is an important part of building modern applications, especially when you interact with REST endpoints.
This 'feature' have been around for a long time, but I don't see any articles on it so I thought I would make everyone aware.
, Continuous Integration
, Development Environment
, Object Data Model
, UI Development
, InterSystems IRIS
, InterSystems IRIS for Health
, Open Exchange
ˮ This is one of my articles which was never published in English. Let's fix it!
This is the first in a pair of articles on SQL indices.
Part 1 - Know your indices
ObjectScript has at least three ways of handling errors (status codes, exceptions, SQLCODE, etc.). Most of the system code uses statuses but exceptions are easier to handle for a number of reasons. Working with legacy code you spend some time translating between the different techniques. I use these snippets a lot for reference. Hopefully they're useful to others as well.
I loaded 2017.2 onto a windows desktop that I was going to use for testing. I need to now uninstall 2017.2 but when I do I get a ERROR saying it can not find the INSTANCE name, when there is HEALTHSHARE defined.
Has anyone else had this issue? I would like to uninstall this version and start over from scratch without having to re-image my machine.
Not everyone knows that InterSystems Caché has a built-in tool for code profiling called Caché Monitor.
Its main purpose (obviously) is the collection of statistics for programs running in Caché. It can provide statistics by program, as well as detailed Line-by-Line statistics for each program.
Using Caché Monitor
Let’s take a look at a potential use case for Caché Monitor and its key features. So, in order to start the profiler, you need to go to the terminal and switch to the namespace that you want to monitor, then launch the %SYS.MONLBL system routine: