Thank you, @Jonathan Lent ! Pleasure to hear we are still better in some spaces than bots :) 

Great points, Dima. But I think any discussions make sense - this is how people communicate and exchange ideas, as you did in your post as well. We could request ObjectScriptQuality to add a profile that will enforce the rule and also, there is a linter in VSCOde ObjectScript - maybe it is possible to request the change in it too.

The idea of an open-source parser for ObjectScript - a good one, do we have it published on the ideas portal?

Voted.

This is great, @Ben Spead! Could you please provide an example of how any developer can leverage the code guidelines @Robert Barbiaux suggests in this post? 
 

I see that coding guidlines for ObjectScript linter should be a document (json? yaml?) you include in your code  repository or reference any file in a github/gitlab and VSCode linter follows it on-the-go.

Or as some ObjectScript.Quality like ruleset, is it possible @Daniel Tamajon ?

Or as a codetidy feature by @Timothy Leavitt, but it's not easy to use.

I see, makes sense

a really helpful repo, @Sylvain Guilbaud ! do you want to publish it on OEX? Please? )

It works because you published a question on Developer Community :) (Joking, of course :)

Jokes aside - a very helpful discussion! Thanks @Sylvain Guilbaud !

In anyways, there are folks on the community that can help even with these already undocummented stuff )

I guess DC AI bot takes only the post body into the consideration thinking the title is a summary of the post. I this case title is one question and post body is another one.

Thanks @David Hockenbroch !

An almost ideal pattern to run an SQL query in ObjectScript. 

If you could also share with error handling around?

My typical pattern looks like this one below. Includes try-catch in case when I need to rollback something:

try {

set tStatement = ##class(%SQL.Statement).%New()

set query = "ALTER Table "_table_" ADD PRIMARY KEY ("_column_")"$$$TOE(st,tStatement.%Prepare(query))

set rset=tStatement.%Execute()

if rset.%SQLCODE < 0 {

write"Error adding primary key: "_rset.%SQLCODE_" "_rset.%Messageset ex=##class(%Exception.SQL).CreateFromSQLCODE(rset.%SQLCODE,rset.%Message)

$$$ThrowStatus(ex.AsStatus())

}

}

catch ex {

set st=ex.AsStatus()

}

Thanks for sharing, @Stephen Canzano!

%expression - is a really impactful feature that can greatly help to tune performance while cubes building.