Hello and welcome to the October 2023 Developer Community Newsletter.
General Stats
154 new posts published in October:
25 new articles
39 new announcements
85 new questions
5 new discussions
234 new members joined in October
12,229 posts published all time
10,555 members joined all time
1 0
0 156
Hello and welcome to the September 2023 Developer Community Newsletter.
General Stats
161 new posts published in September:
35 new articles
40 new announcements
78 new questions
8 new discussions
217 new members joined in September
12,075 posts published all time
10,343 members joined all time
0 0
0 112
9 4
1 413
Article
· Jan 25, 2016 1m read
2016.2 Field Test

I am pleased to announce the field test of Caché and Ensemble 2016.2 - an exciting new release with improvements on many different fronts.

The entire product team at InterSystems looks forward to your participation in the field test and feedback over the coming months.

Some of the more profound changes in 2016.2 include:

6 6
0 1.1K

Hi everyone,
I have this global with 2 informations in it: Reference (ex: 1329) and Code (ex: JMMK-G1D6).

^DataTest = 3
^DataTest(1) = $lb("","1329","JMMK-G1D6")
^DataTest(2) = $lb("","1516","AMEV-GVPF")
^DataTest(3) = $lb("","2333","4QC6-4HW3")

With ObjectScript, i want to test if Reference 1516 exists in the global.
In the InterSystems portal, i can do it with SQL (SELECT count(*) FROM DataTest where Reference = '1516'), but can we do the same in ObjectScript without SQL and manipulating the global directly ?

0 3
0 19

Hi,

I was struggling with a procedure that was meant to receive a string and use it as a filter, I've found that since I want the procedure to do some data transformation and return a dataset, I needed to use objectScript language.

I've created the procedure using the SQL GUI in the portal, and everything works fine when calling the procedure from the SQL GUI but not through a JDBC connection here is the call "call spPatientOS('2024-04-07T12:35:32Z')"

3 2
0 107
InterSystems Official
· Nov 9, 2023
InterSystems IRIS Minimum Supported CPU Models

When AMD published the x86-64 standard in 1999, little did they know they were inventing what would become the de-facto architecture for server CPUs. But the CPUs of today aren’t the same as ones produced 20 years back – as they have extensions for everything from Advanced Vector Extensions (AVX) to Hardware-Assisted Virtualization (VT-d).

InterSystems would like to take better advantage of these new extensions in upcoming versions of InterSystems IRIS. While our compilers are smart enough to create optimized code for many situations, some optimizations can only be turned on by explicitly cutting off support for processors that do not have that instruction set. Additionally, we are finding it increasingly difficult to maintain older CPU models to test on.

3 8
5 584