I'd say it's a bug in Query Generator.
A workaround in DB-API just might hide the real cause.
If you are lucky the bug is fixed by the next release or the next after or some future release
- Log in to post comments
I'd say it's a bug in Query Generator.
A workaround in DB-API just might hide the real cause.
If you are lucky the bug is fixed by the next release or the next after or some future release
I fail to imagine how to do this with ePy ![]()
thanks for confirming my diagnose
- that's why I used "+id as id1" to break the link to index global
- and :BTW: ORDER BY 1 ; just using column position shows the same bug
set claim=##class(Claim).%OpenId(claimnum) ; or similar set line=##class(ClaimLine).%OpenId(linenum) ; or similar do claim.ClaimLineRel.Insert(line)
now your query should work
Why would you want to do this?
the index related to %Save() is no "build" but just setting a value to the index global.
setting an index is mostly less load than saving an object.
@Laurel James (GJS) You are very welcome!
I publish ANY review that I'm able to identify. Not just my own, which are easiest to find.
see this article: Date before Dec.1840 ? Negative $H(orolog) ?
A possible workaround
SAMPLES>set rs= ##class(%SQL.Statement).%ExecDirect(,"SELECT +id id1, x, y, z FROM some_table ORDER BY id")
SAMPLES>while rs.%Next() { zwrite$listbuild(rs.id1, rs.x, rs.y, rs.z) }
$lb(1,1,2,"z1")
$lb(2,2,3,"z2")
$lb(3,3,4,"z3")
$lb(4,4,5,"z4")
SAMPLES>
The point is to consume your value NOT from temp order global.
tested in
Cache for Windows (x86-64) 2018.1.7 (Build 721U) Fri Mar 18 2022 22:07:35 EDT
Should also work in IRIS
terminate your Dockerfile with USER irisowner as last line
and code quality will struggle with it and dislike it
because you use name in write, but you don't set it explicitly
but don't care much about:
it doesn't understand %-variables and global variable scopes
and $$$macros with code inside, and ... and ... and
to get control over your situation you have 2 key methods:
So you have to check if your user has exhausted its available connections and block him.
It's anyhow quite interesting how these users are able to trigger so many connections.
This is intentional behavior.
If the routine you changed calls some subroutine it is kept "on the stack"
This is a requirement to have a save return and continuation after the call.
The new version only becomes active after you have left the previous one by QUIT or RETURN.
simpler: if it is gone from the return path.
I share your suggestion!
When I started with Docker I was highly skeptical after many years with VMware starting before their first release.
It was a hard exercise and I took quite a while digging through docs and helps.
My main problem was that everything was so generic and not at all specific to IRIS (or Caché).
Meanwhile, it became so common to me that I stopped running reviews on packages without docker.
Docker allowed me to have a "clean desk" after testing.
In addition. I saw through this activity so many valid variations that
I doubt to decide how to start and where.
On the other hand, I see in OEX ~450 tested and working examples (a dozen PR still pending)
Following these examples and trying to understand what will be achieved
could be good food for training designers.
You may have only 1 command: in each build
the 2nd overwrites the first
iris:
image: intersystemsdc/iris-community:latest
command: --check-caps false
container_name: tls-ssl-iris
networks:
app_net:
ipv4_address: 172.16.238.20
volumes:
- ./iris-config-files:/opt/config-files
# Mount certificates files.
- ./certificates/CA_Server.cer:/usr/irissys/mgr/CA_Server.cer
- ./certificates/iris_server.cer:/usr/irissys/mgr/iris_server.cer
- ./certificates/iris_server.key:/usr/irissys/mgr/iris_server.key
hostname: iris
# Load the IRIS configuration file ./iris-config-files/iris-config.json
command: ["-a","sh /opt/config-files/configureIris.sh"]
this worked as multi-line
command:
- -a
- sh /opt/config-files/configureIris.sh
- --check-caps false
BUT
command: ["-a","sh /opt/config-files/configureIris.sh","--check-caps false"]
works as well
nothing prevents you to load this script at runtime from server.
<script src="myscripts.js"></script>
from w3schools.com https://www.w3schools.com/tags/att_script_src.asp
So you are outside your Caché
I do the same exercise in my package GlobalToJSON-ePython-pure
it should be basically sufficient to replace the JSON packing + writing by print(...)
see >>> def node(nd,nxt,fil):
in my various examples I took these strategies:
to my experience, your 'KeyError' indicates that you try to get a value
from a non-existing global or subscript. in COS it would be <UNDEF>
in my package GlobalToJSON-ePython-pure
I developed this workaround:
#; simulate $data() for existence and contentdefDdata(gref):
val = None
_d = 11#; check for subscripts
o=gref.order([])
if o == None:
_d -= 10try:
val=gref.get([])
except KeyError:
#; no value @ top node
_d -= 1return [_d,val] NIce you share a picture of a PDP11 !
a few of my heroes:
---
I know also some handicapped developers.
BUT: I find it highly insensitive and inadequate to drop their names in this forum
Any sport that requires mental concentration. eg. mountain climbing,
And I mean REAL climbing, not just moving your body somehow across nature.
With 2 very successful sons in software, internet, and project engineering (49yrs. + 36yrs.)
I have a valid benchmark for my strategy.
A real software developer doesn't care about the hardware or operating system.
Specific hardware is a subject for gamers.
I use and just verifiied
iris.cls(__name__).SetupGame()
I enjoy to solve what was declared to be IMPOSSIBLE before.
I dislike it if it turns out that issue was just a fake and nobody cares about my creations.
--progress plain
This is essential information.
Without it the building log just runs though with no chance for a rollback
and iris.script allows a lot of temporary debugging info.
my PR contains an update on docker-compose.yml
and a bash script startflask.shall available here https://github.com/rcemper/iris-python-flask-api-template
Sep.23 all merged