go to post Iryna Mykhailova · Jan 19, 2024 Oh, wow! It's so cool to be recognized not in 1 but 2 nominations! Congratulations to everyone!
go to post Iryna Mykhailova · Jan 9, 2024 Wow, this is really cool in a very scientific kind if way.
go to post Iryna Mykhailova · Jan 5, 2024 For something like this, you can use a Learning Lab, it's free: https://learning.intersystems.com/course/view.php?id=929
go to post Iryna Mykhailova · Dec 30, 2023 Congratulations to the winners! Well done! Hope you had fun doing all the daily challenges!
go to post Iryna Mykhailova · Dec 26, 2023 I'd agree with @David Hockenbroch - if you have a UI, you will most likely find it easier to work with a csp page like a usual html and all that. But if you don't have a UI (or it's super simple), then you would create a cls file and extend the %CSP.Page.
go to post Iryna Mykhailova · Dec 4, 2023 Congratulations to all the winners and participants, particularly to @Anna Diak and @Andrii Mishchenko - I am so very proud of you!
go to post Iryna Mykhailova · Nov 30, 2023 It's a shame, I feel like there is often something going on with Cloud SQL. Especially during contests 😄 That's why I don't feel confident to incorporate it in my course 😢 - I ask my students to use it and then they can't even set it up without a fuss.
go to post Iryna Mykhailova · Nov 17, 2023 The command doesn't know. That's why you need to check the SQLCODE variable. If SQLCODE = 0 then the row exists and it was updated. If SQLCODE = 100 then the row doesn't exist. If it not equal to either then you have a problem. Example for Embedded SQL: &SQL(update WH.Size set Height = 1000 where %ID = 10) write SQLCODE Example for Dynamic SQL: SET myquery = "update WH.Size set Height = 1000 where %ID = 10" SET tStatement = ##class(%SQL.Statement).%New() SET tStatus = tStatement.%Prepare(myquery) SET rset = tStatement.%Execute() write rset.%SQLCODE Not sure what you mean by "if the row exists" in regards with insert. The row does not exist, because you're creating it.
go to post Iryna Mykhailova · Nov 14, 2023 I'd say in general, having a structured data with the actual names of fields is much better than "parsing" the text with delimiters. So I would vote for FHIR. Maybe at some point there will be a better way to represent data - and it is OK - and people will switch to it. The main idea - not to make it painful on the developers to rewrite everything!
