in the previous screenshot you see the namespace as a blue link
and the names of the DB in the yellow highlighted  
 

check if the date object  var d=new Date();
is inside your routine or at least globally defined

like this

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

applying  

• WITH STORAGETYPE = COLUMNAR

as last line  item seems to work (as found in Docs)

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

• ...   ("VERSION")),".",1,2)<2013.1  ..... 
• ...  Set sc=$$$ERROR($$$DplyVersion, .....
• %occErrors.inc(2547): #define DplyVersion 7602

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:

• Oracle takes a lot of effort to prevent straightforward comparisons
• But over decades, I haven't ever seen them winning against IRIS / Caché.
• OK, and PostgreSQL or MySQL never was competitive,

Great job !

What You See Is What You Get

#1)  what type of "routine" do you try to handle ?

• .cls
• .mac
• .int
• .obj

#2) what is the Format you get those "routines"

• .ro
• .xml
• .udl

some combinations may allow  "command line" examination 

In ENSEMBLE default namespace SAMPLES holds a collection, CSP examples.

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.

• keep memory consumption low
• data transfer between memory and "disk" (or what mimics a disk) is the the slowest component of your system (except human user) so keep it as flat as possible

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