eventually terminal in *UX may end just with $c(10)
could you try to append some blank + semicolon ?
:alias enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L")) ;You seem to lose the last character
- Log in to post comments
eventually terminal in *UX may end just with $c(10)
could you try to append some blank + semicolon ?
:alias enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L")) ;You seem to lose the last character
I agree with @Brett Saviano:
$$$ ...refers to some #define ... and is a compiler directive
I tried:
USER>:alias wi write "/csp/"_$zcvt($namespace,"L")
USER>:wi
write "/csp/"_$zcvt($namespace,"L")
/csp/user
USER>:alias wi1 write "/csp/"_$$$LOWER($namespace)
USER>:wi1
write "/csp/"_$$$LOWER($namespace)
WRITE "/csp/"_$$$LOWER($namespace)
^
<SYNTAX>
USER>👍 SUPER 💪
from my local Class docs:
GetGlobalSizeBySubscript
This method will return the size of a global based on the number of database blocks the global resides in.
so you get blocks * blocksize ===> ALLOCATED size
Depending on Packing as %GSIZE shows The difference might be significant
Summary by Subscript will most likely show higher values as a pointer block
or even a data block (eg. with 8kb) may contain more than a single subscript
depending on the Global structure.
Take the default top subscript (aka. IDKEY) for Caché classes (Integer, >0) as an example
tSC is mostly a %Status object
with enough experience Zwrite tells you all you want and need to know
$SYSTEM.Status.DisplayError(tSC) is easier read. a matter of comfort
ChatGPT is just stupid and has no idea of IRIS / Caché
A TABLE will by default never have the same name as the GLOBAL that stores the content
>>>> HS.IHEX.RecordHistory and the global ^HS.IHEX.RecordHistory <<<<<
HS.IHEX.RecordHistory is definitely not a handcrafted table.
Thanks for the recognitions! 😀🖐
It's a very strong motivation to be productive.
Often to distract from personal struggles.
Many thanks to the DX+OEX+GM team for their help! 👏 🌸🌼🌹🌻💐
Hi @Daniel Aguilar
for every DB you have a default collation that is tied to DB:
you can see it in SMP System > Configuration > Local Databases > Database Properties.png)
this is the standard.
If the collation of your source server is Spanish, German, Fench, , ....
the DB may have used this national collation as default.
On your target serve you need to have this collation to be installed.
in SMP System > Configuration > Locale Definitions you see what is installed on your Caché instance.png)
You may need to add the missing collation table to your Caché instance:
.png)
in the previous screenshot you see the namespace as a blue link
and the names of the DB in the yellow highlighted
Just as described in your question
check if the date object var d=new Date();
is inside your routine or at least globally defined
like this
.png)
take a look to Mgmt Portal and check NAMESPACE definition
to see DB-file vs. Namespace.
In your case, I'd create a new namespace based on your DB-file to avoid conflicts.
>>> the same Db for Routine (=code) and Globals
Big CONGRATULATIONS to all winners !
It's a pleasure to follow your contributions.
right. 2013.1 was the last chance
%Studio.Project).InstallFromGbl(... rejects explicitly for Versions before 2013.1 in line 1440
You better contact WRC for help with this 10 year old version
Bonsoir Sylvain!
Are you looking for something similar to this;
Property MonJour As %String
[ InitialExpression = "31/12/1840" ];
Property Jour As %Date [ InitialExpression = 0,
SqlComputeCode = {set {*}= $ZDH({MonJour},4) },
SqlComputed, SqlComputeOnChange = MonJour ];
(Multiline just for readability)
Thanks for the test data!
It confirms known behavior:
Great job !
What You See Is What You Get
#1) what type of "routine" do you try to handle ?
#2) what is the Format you get those "routines"
some combinations may allow "command line" examination
In ENSEMBLE default namespace SAMPLES holds a collection, CSP examples.
there is a basic misunderstanding:
inside the <CSP:WHILE...> block you are in HTML context
but you issue instead JavaScript >>>> which just prints it out.
To illustrate this see this simple example:
But changing to JS_context solved my simple demo with alert();
<csp:WHILE CONDITION="resultSet.Next()">
<!-- xValues.push(#(resultSet.Get("StatsDate"))#)
yValues.push(#(resultSet.Get("Value"))#) -->
<p>#(resultSet.Get("StatsDate"))#<br>#(resultSet.Get("Value"))#</p>
<script LANGUAGE="JavaScript">
alert(#(resultSet.Get("StatsDate"))#+'>>>'+#(resultSet.Get("Value"))#);
</script>
</csp:WHILE>Puoi dare un suggerimento in Ideas Portal
Penso che ci sia abbastanza supporto lì.
Perciò ?? @Luca Ravazzolo ??
Great Stuff!
This matches seamlessly to the "real" Customer benchmark I did in 2009 (with Caché)
against PostgreSQL and MySQL
Years went by but the principles haven't changed.
Glad to see that this is still as valid as it was since ever.
After so many years, all new technology tricks didn't change that.
find One-Line-Installer here ZPM is rather on top
It is still in IPM. OEX seems to have lost it. ???
zpm:USER>search global-dump-sql
registry https://pm.community.intersystems.com:
global-dump-sql 1.0.2
zpm:USER>install global-dump-sql
[USER|global-dump-sql] Reload START (C:\InterSystems\IRIS\mgr\.modules\USER\global-dump-sql\1.0.2\)
[USER|global-dump-sql] Reload SUCCESS
[global-dump-sql] Module object refreshed.
[USER|global-dump-sql] Validate START
[USER|global-dump-sql] Validate SUCCESS
[USER|global-dump-sql] Compile START
[USER|global-dump-sql] Compile SUCCESS
[USER|global-dump-sql] Activate START
[USER|global-dump-sql] Configure START
[USER|global-dump-sql] Configure SUCCESS
[USER|global-dump-sql] Activate SUCCESS
Just providing the global name results in a full global dump.
Example:
USER>zn "user"
IRISAPP>d $system.SQL.Shell()
SQL Command Line Shell
... select TOP 5 * from zrcc_G.dump where zrcc_G.Dump('^%SYS','"JOURNAL"')=1
Thank you Maksym !
You reached 100% ObjectScript.
I was really impressed by your Part2 on day 23 + 24