AFAIK Try/catch indeed slows a bit the execution (@Dan.Pasco is it true?)

And try/catch shouldn’t be presented in every method - it could be somewhere on top and in the places where you need to catch errors.

I like your answer but for better understanding it deserves a sample code to see how do you manage error scenarios.

we really lack of good templates for beginners on how to better handle errors in serious project.

Thanks for the insights, @Herman Slagman!

$ZT + Label is better than try/catch

%Status is better than try/catch too.

why %Status is better than throw ("something went wrong") approach?

But, how to do you track errors of your solutions happen on a customer side? There is an elegant way to manage this with try/catch:

catch e {

 do e.log() // store the error and stack in Application Errors

// handle error

} 

How could you manage this with %Status and $ZT approach?

Thanks, Jon!

Why try-catch doesn't work well without finally? I think finally is only for the cases when you need to free resources taken, isn't it?

Thanks for the answer, Gertjan!

May I ask you, why don't you like try/catch? Is it slow?

Imho it has all the error and stack information, what's wrong with try/catch?

I think if the method should return something else, it should return not %Status but the value.

Thanks, Steve!

Thanks, Ben!

This is another good topic for discussion on should the test code be included in the production

You've just posted an article!) I wasn't aware too.

We need to check and maybe we'll include this as well!

We may add more bonuses - the contest will start next Monday, we still have time to add more ;)

I respect your choice. Out of curiosity, what other than SQLCODE variables you noticed being changed "without a warning"?

On contrary, I started to find it handy to copy and paste working sql into &sql(). Also, SQL code looks more readable.

And we changed it one more time.

Now the proper switch to the test repo is:

repo -n registry -r -url https://test.pm.community.intersystems.com/registry/ -user test -pass PassWord42

The text in the article is updated accordingly

iris-fhir-portal uses FHIR SQL Schema now.

More details.