Path is how you access the value.
- Log in to post comments
Path is how you access the value.
Contact your Account Manager at InterSystems.
Usually I do this:
set sc = ..method()
/// finalization
quit:$$$ISERR(sc) scI always use %Status and try to wrap calls in this macro:
#define qoe(%expr) $$$QuitOnError(%expr)For example:
$$$qoe(..computeDigest(canonicalized))$$$ERROR($$$SQLError, SQLCODE, %msg)You can use PythonGateway to call Python code from InterSystems IRIS directly.
Example:
set sc = ##class(isc.py.Main).SimpleString("x='HELLO'", "x", , .x)
write x
>HELLOYou can start with
set %gw = createJavaGateway()Where createJavaGateway is
ClassMethod createJavaGateway()
{
quit:$d(%gw) %gw
/// init connection
}And remove disconnect part. This way %gw variable would stay alive betwee the calls.
Is the response actually compressed?
I thought automatic decompression is happening a few layers down on the stack.
Use session id to track data between calls.
In general I would suggest moving to REST stateless architecture.
Try serving files from
<IRIS>\mgr\Temp\directory.
By default InterSystems IRIS runs under system account which does not have access to your user account folders.
I prefer
johndoe.test.lib.classAs long as storage aligns, you can use this approach.
Calling @Anton Umnikov
How are you planning to determine to which service the message should go?
Probably 3,641,144.
Calling @Dan Pasco
Here's how you can add your ObjectScript snippents to VSCode.
They are usually Stored in:
C:\Users\<USER>\Documents\Intersystems\CodeSnippets.txtIf they are not there open Studio -Instruments - Parameters - Environment - Code Fragments
The file path would be there:
.png)
Which version are you on?
Pleas port relevant parts of ExecuteResult class.
If the user does not have W access on routines db he will not be able to edit it.
Also the whole DB might be marked as RO.
Sure:
Set sc=##class(%REST.API).GetWebRESTApplication(namespace,webApplication,.swagger)Can you elaborate a bit?
What dispatcher class do you want generated?
Dmitriy is correct but for your specific use case (auto-removed globals) use Process Private Globals as they are automatically deleted on process end.
Do you want to search at storagetime or at runtime?
%Compiler package can do that but it's not supported.