All
Accepted answers
Robert Cemper · 16 hr ago go to post

As my 5* review in OEX is still blocked after fixing 
a minor typo in text I'lll publish it here.
-----------------------------------------------------------------------

Robert Cemper · Feb 25 go to post

method jsonstring() is missing a return value
suggestion
ClassMethod jsonstring(id, map = "") As %String [ SqlProc ]

The rest is working perfectly
The use of customized mapping was new to me 
Excellent improvement and very useful
Expect my review on OEX

Robert Cemper · Feb 25 go to post

The idea of 

set ^A($char(65535)) = ""

Looks good at first sight, but this might be the next follower

set ^A($char(65535),0) = ""
Robert Cemper · Feb 22 go to post

Just great !
and an incredible consumption of resources on disk and cpu
with my Windows Docker Desktop 
😎
  

Robert Cemper · Feb 22 go to post

Hi O.K.,
Thanks for reading the details.
OEX admins decided to merge the better package with the previous.
As a consequence, my review was just gone, and the link pointed to nowhere
Though experienced by >780 reviews accepted by OEX censors, I had a private copy
The link is adjusted, and the saved review is published again.

Robert Cemper · Feb 21 go to post

list display failed at that point also text was scrambled
now it's working normal again

Robert Cemper · Feb 17 go to post

So it's clear.
Old_Class loads old defined properties in a local Object structure 
and writes only this structure back.

It has no idea of New properties and doesn't write it.
Just a guess:
$LB(...) in ^GlobalD of Old_class is shorter than for New_class
 So %Save() of Old_class is a data killer.
 

Robert Cemper · Feb 17 go to post

OK,
but prerequisit is, that both definitions are identical.
Especially in the Storage definition, where properties are mapped to globals

Robert Cemper · Feb 17 go to post

ATTENTION ! This made me nervous.

In essence, the two classes are sharing the same data / Index / stream globals.

This means there is also
Parameter MANAGEDEXTENT As INTEGER = 0;
Otherwise, it wouldn't compile

Robert Cemper · Feb 17 go to post

Re-reading your question, I understand that properties in 
New_class are not identical and synchronized with Old_class ?
So even Storage Definition might be different ? 
IF YES, I'd say it's highly risky! 

Robert Cemper · Feb 17 go to post
  • With %OpenId you create a complete internal local copy of your object
  • With %Save it is written back as complete as is was. NOT just changed properties as you might expect And non- defined properties vanish
  • Any change that happened in between from some other process is lost
  • You may need some locking logic to prevent simultaneous access by 2 instances  eg. locking the Id for exclusive access by 1 single  process.
  • In your case it may even happen in 1 process with Old_Class vs, New_Class
Robert Cemper · Feb 17 go to post

Big Thanks for this recognition  ! 
Especially for the team that made it possible. 

💐 

Robert Cemper · Feb 15 go to post

Does it work without that UnitTest line in the Dockerfiles ??

 ([ $TESTS -eq 0 ] || iris session iris -U $NAMESPACE "##class(%ZPM.PackageManager).Shell(\"test $MODULE -v -only\",1,1)") && \

Running UnitTest directly in iris.script might be easier to control.
Checking UnitTests with ZPM manually after the first install might give more precise info of the problem
 

Robert Cemper · Feb 12 go to post

My personal approach would be:

  1. separate instance code from Class Methods
    This covers all properties and especially Calculated Properties
    Or simplified, all code tied to data storage
  2.  Class Methods work on referenced objects but have no dedicated data store (i%...)
    Simplified, they are code-only components.
  3.  Class Methods could be bundled in several Classes.
Robert Cemper · Feb 10 go to post

In Caché you had CacheParameterFile  cache.cpf with the SuperServerPort 1972
now it's named iris.cpf  with DefaultPort=1972

Robert Cemper · Feb 6 go to post

@Julius Kavay  hits the point:

true of false as system constants is breaking the rules and
the long-practiced idea and principles behind ISOS and before
( @Joel Solon : isn't it ?) 

You may ask for $TRUE or $FALSE  system constant / variable

Until this, you are free to define your own $ZTRUE or $ZFALSE using
%ZLANGV00.mac to extend the language.
It's all ready for use to extend the language according to your needs and taste

Details on %ZLANG*

Robert Cemper · Feb 6 go to post

I fail to see the problem:

  • true:==> $$$OK
  • false:==> $$$NOTOK

do I miss siómething ?

Or is the intention to mix ISOS with JavaScript ???

Robert Cemper · Jan 27 go to post

Primary / Secondary  ?? Is this a shadowing configuration ?

Shadowing applies to the databases  IRIS.DAT, and Journal Files  
It doesn't shadow external "foreign" files like  .../Temp/QWhoZAwFF3f9jQ.iostream

Robert Cemper · Jan 20 go to post

If you use a custom class query %Library.Query type you may write your parameters to some
^mtemp.Evgeny($i(^mtermp.Egeny)) = ..... direct from the Execute method
or ^mtemp.Evgeny($h) = ....

For basic class query %SQL.Query () you may take the usual SQL approach

  • Create a SQL method that always returns 1 (TRUE)
  • You pass all your parameters into that method 
    • which does the ^mtemp trick and a QUIT 1
  • add to the WHERE clause  . . .  AND MYTRACE(par1,par2,---)=1

I refer to this a STATIC clause since it is only executed once by query
because of no reference to any column values 

It was my approach to SQL debugging