You can try just SQLPROJECTION = "table/column" but I highly recommend testing it first.
- Log in to post comments
You can try just SQLPROJECTION = "table/column" but I highly recommend testing it first.
If there's no data yet, project it as a table:
Property CodeTable As list Of Sample.CodeTable(SQLPROJECTION = "table/column", STORAGEDEFAULT = "array");Looks like I'm a golfer this year.
.png)
You can set it programmatically:
set package = ##class(%PackageDefinition).%OpenId("User",,.sc)
zw package
package=2@%Library.PackageDefinition ; <OREF>
+----------------- general information ---------------
| oref value: 2
| class name: %Library.PackageDefinition
| %%OID: $lb("User","%Library.PackageDefinition")
| reference count: 2
+----------------- attribute values ------------------
| %Concurrency = 1 <Set>
| ClientName = ""
| Description = ""
| GlobalPrefix = ""
| Name = "User"
| OwnerName = ""
| RtnPrefix = ""
| SQLName = ""
+----------------- swizzled references ---------------
| i%list = "" <Set>
| r%list = "" <Set>
+-----------------------------------------------------Thank you!
Just never seen force to be completed under 2 seconds.
Is it possible to trigger fast shutdown without stopping the OS?
XSLT unless we are talking about a very large files to be processed very quickly in which case SAX parser might be worth a consideration.
Can you show an example of source ASTM file and a resulting HL7 you want to get, please?
Are you getting Ens.StreamContainer?
It would be
I would try a password with just a-z, A-Z, 0-9, !#$%^&*()[]{}. Maybe there's some issue with wide characters?
You need a restart following this rename. Also try to replace cgateu.so with cgateur64.so.
Any chance user has multibyte unicode characters in the password?
Users should not add new %SYS classes though.
Nice! What performance hit are we talking about? No way this level of detail is free.
%ALL namespace is another way to share routines/classes globally but without the need to modify CACHELIB/IRISLIB.
DSN must be defined in <iris>/mgr/irisodbc.ini
Encountered similar issue:
ERROR #743: CA certificate file is not valid [%OnValidateObject+97^Security.SSLConfigs.1:%SYS]
Turns out, Extension:basicConstraints field of the CA certificate must contain CA:TRUE. The BasicConstraints extension is intended primarily for CA certificates. It has a single Boolean variable, “cA”, which reflects whether or not the certificate is a CA certificate. If the certificate is a CA certificate, it can also declare a pathLen constraint that dictates how many sub-CAs are allowed to exist in the hierarchy of CAs.
To check:
Set bc=$System.Encryption.X509GetField(cer,"Extension:basicConstraints")
Write bc["CA:TRUE"Nice!
Add %JSONIGNOREINVALIDFIELD param to your class and don't add Messages/SharedRelations properties.
Parameter %JSONIGNOREINVALIDFIELD As BOOLEAN = 1;Why not just use %JSONFIELDNAME?
Anyway, this works:
Property "@name" As %String;
Property "😋_are_you_sure_😋" As %String;Is CDATA actually getting sent or is it just a visualization issue?
I suppose you can use HS Trace operation or IO logging to get the raw output.
Try to start Remote Gateway from the SMP and check the error there. Current error you see is caused by the fact that Gateway is not started or IRIS can't connect to it.
You need CONTENT=ESCAPE instead of CONTENT=STRING. Here's an example:
Class Utils.XML Extends (%RegisteredObject, %XML.Adaptor)
{
Property PACPROBLEMAS As %String(CONTENT = "ESCAPE", MAXLEN = "", XMLNAME = "PAC_PROBLEMAS");
/// do ##class(Utils.XML).Test()
ClassMethod Test()
{
set obj = ..%New()
set obj.PACPROBLEMAS = "1<2"
do obj.XMLExportToString(.xml)
zw xml
}
}Produces:
<XML><PAC_PROBLEMAS>1<2</PAC_PROBLEMAS></XML>
That is the recommended approach.
I'm using AWS SNS (via Embedded Python) to send notifications by SMS.
What's "RO" stand for?
ReadOnly.
After the customer deployment, if there is any change made on the production settings (e.g. changing an AE Title on the DICOM service), those settings are stored in the APPCODE, and the settings will be lost after a container PODS restart (kubernetes recreating the PODS).
Two ways to avoid that:
Great article!
For cases, where you don't want to share the source at all (even if it's immediately deleted), the following approach would work:
1. On your system (with source code) execute:
set p=##class(%Studio.Project).%New()
do p.AddItem("WH.Color.cls")
do p.AddItem("WH.Size.cls")
do p.DeployToFile("c:\test\app.xml",,1)It will create an XML export with object code only and no source code included.
2. Transfer the file into a target system and execute:
set sc=##class(%Studio.Project).InstallFromFile("c:\test\app.xml")APPCODE must be RO if you want to leave it in the container to be replaced as a part of the container.