- Log in to post comments
User bio
404 bio not found
Member since Oct 23, 2023
Posts:
Replies:
Use 'Return' instead: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_creturn
In general, if you're trying to exit a method and return a value to the caller, 'Return' is the best way to do that, as 'Quit' also has functionality for control flow (such as breaking out of WHILE loops).
- Log in to post comments
Hmm, that's not what I would have expected. I'm going to ask around and see if there's something I'm missing here, but in the meantime can you try running TUNE TABLE on this table and see if that changes the behavior/query plans at all? https://docs.intersystems.com/iris20253/csp/docbook/DocBook.UI.Page.cls…
- Log in to post comments
Certifications & Credly badges:
Nick has no Certifications & Credly badges yet.
Followers:
Following:
Nick has not followed anybody yet.
I think this is something that heavily depends on your use case, but in general I would just stick to typical Object-Oriented Programming best practices (e.g. SOLID) and try to aim for a level of abstraction that fits your application. If your different integrations use the same types of information, then having them reuse the same message classes makes sense to me.