It is worth mentioning that the "DATEDIFF" function does not always calculation as expected, eg:

>w $system.SQL.DATEDIFF("yy",$zdh("31.12.2022"), $zdh("01.01.2023"))
1
>w $system.SQL.DATEDIFF("mm",$zdh("31.12.2022"), $zdh("01.01.2023"))
1

This is stated in the documentation for SQL DATEDIFF

You might find it interesting to download the Community Edition <..> and see if the bugs you reported are still present there or not. What do you think about that approach?

<..> we still create an SU version of Caché <..> because some of our large partners/APs rely on it for people to learn on <..>

I have already written that, as well as your large partners/APs who prefer to stay on Caché, IRIS does not interest me in this case.
Why would I check something that I won't be using in the foreseeable future, even if there are fixes there?

And yes, for the sake of hobby, I have been using IRIS CE for a long time.

Hi Jeffrey.

By far the vast majority of users that want Caché are existing customers - so you can get this easily through the WRC.

I have indicated why I already can't get Caché now, even the SU version:

<..>, until the technical support ended.
<..> in future versions of Caché, which I can no longer check.

you could download the Community Edition of InterSystems IRIS and just install Studio from that if you wish

That's exactly what I'm doing now. But agree, downloading hundreds of megabytes for the sake of Studio and drivers is inefficient.

Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition

IRIS does not interest me in this case.
Over the years I have "tormented" WRC about the bugs I found in Caché (in some way I acted as a free beta tester), until the technical support ended.
Some fixes at that time were included only in future versions of Caché , which I can no longer check. I would be interested to check out these fixes on the free version.

Maybe there are other reasons why there is still a single-user version of Caché, especially only for those who already have a full-featured version, but for me they are not obvious.

Do I understand correctly that Caché Evaluation and IRIS Studio (full kit) are only available through WRC, which is not available to everyone, but only for supported customers?
It seemed to me that these products are designed for everyone.
By the way, the same goes for ODBC, JDBC and CSPGateway.

I decided to check the size of the code using an officially allowed method.

ClassMethod length(
  class = {$classname()},
  method = "Solve") As %Integer [ CodeMode = expression ]
{
##class(%Dictionary.MethodDefinition).IDKEYOpen(class, method).Implementation.Size
}

So,

size = 46 (43)

ClassMethod Solve(o As %String) As %Integer
{
 f  s c=$p(o,",",$i(i)) q:'$lf($lfs(o),-c) c
}

size = 48 (45)

ClassMethod Solve(o As %String) As %Integer
{
 f  s c=$p(o,",",$i(i)) ret:'$lf($lfs(o),-c) c
}

So, the author is not lucky and in its version this feature is not available.
It seems you have the wrong addressee, I have 2021.2 :)

I also noticed that in IRIS 2020.1 documentation is nothing about 'ALTER COLUMN RENAME' syntax.

Yes, check alter-column-action ::=
2020.1
2021.1

Good trick!

size = 47

ClassMethod Solve2(o As %String) As %Integer
{
a s c=$p(o,",",$i(i)) g:$lf($lfs(o),-c) a q c
}

I have 190 on 1 line.

UPD: Program can be reduced to 189, but at the same time efficiency will decrease. Therefore, I will stop on the value 190.
Let us know when the contest ends and it will be possible to open the sources.

Hope you are talking about Visual Studio Code, not Visual Studio.

It is a pity that the author left the previous task (Code Golf - Encoder) without attention, and the community ignored her (or did not notice;)

size = 49

ClassMethod Solve(o As %String) As %Integer
{
 f i=1:1 s c=$p(o,",",i) ret:'$lf($lfs(o),-c) c
}

Given (IRIS 2021.2):

Class fixxer.decars Extends %Persistent [ DdlAllowed, SqlRowIdName = UniqueIdentifier ]
{

Index iUnq On (brand, MaxSpeed, color) [ IdKey, PrimaryKey, Unique ];
Property brand [ SqlColumnNumber = 2 ];
Property MaxSpeed;
Property color;

}

USER>d $system.SQL.Shell()
SQL Command Line Shell
----------------------------------------------------
 
The command prefix is currently set to: >.
Enter , 'q' to quit, '?' for help.
[SQL]USER>>select * from fixxer.decars
1.      select * from fixxer.decars
 
UniqueIdentifier        brand   MaxSpeed        color
 
0 Rows(s) Affected
statement prepare time(s)/globals/cmds/disk: 0.0020s/5/140/0ms
          execute time(s)/globals/cmds/disk: 0.0004s/1/719/0ms
                          cached query class: %sqlcq.TEST.cls4
---------------------------------------------------------------------------
[SQL]USER>>alter table fixxer.decars alter column color rename color2
2.      alter table fixxer.decars alter column color rename color2
 
0 Rows Affected
statement prepare time(s)/globals/cmds/disk: 0.0153s/2 113/13 157/0ms
          execute time(s)/globals/cmds/disk: 0.1492s/52 206/467 790/0ms
                          cached query class: %sqlcq.TEST.cls5
---------------------------------------------------------------------------
[SQL]USER>>select * from fixxer.decars
3.      select * from fixxer.decars
 
UniqueIdentifier        brand   MaxSpeed        COLOR2
 
0 Rows(s) Affected
statement prepare time(s)/globals/cmds/disk: 0.0741s/38 529/179 560/0ms
          execute time(s)/globals/cmds/disk: 0.0003s/1/719/0ms
                          cached query class: %sqlcq.TEST.cls4
---------------------------------------------------------------------------
[SQL]USER>>

Now:

Class fixxer.decars Extends %Persistent [ DdlAllowed, SqlRowIdName = UniqueIdentifier ]
{

Index iUnq On (brand, MaxSpeed, color) [ IdKey, PrimaryKey, Unique ];
Property brand [ SqlColumnNumber = 2 ];
Property MaxSpeed;
Property color [ SqlFieldName = COLOR2 ];

}

PS: by the way Studio highlights the error in the following code

&sql(alter table fixxer.decars alter column color rename color2)

But the compilation goes without errors.