go to post Evgeny Shvarov · Dec 29 Wow. ObjectScript is like an endless book of surprises :) You never know what you can find the next day :) Don't know if I ever used something like this. For me, #dim can be useful to easily suggest a possible method or property while coding, but good to know about such an option! Thank you @Vitaliy Serdtsev !
go to post Evgeny Shvarov · Dec 28 Thanks @Robert Cemper ! I this case Query was a slightly better alternative to me vs Embedded SQL (more readable SQL). So… But knowing once again that everything is possible is always good, especially a few days before New Year! :)
go to post Evgeny Shvarov · Dec 28 Thanks for the clarification, @Ashok Kumar T ! What can I say - it's not obvious (that it is only for SELECT), and it's a pity as the "Query" functionality that works great for SELECT can also be leveraged with INSERT, DELETE and UPDATE. Sounds like a good candidate for the Ideas portal :)
go to post Evgeny Shvarov · Dec 28 #DIM is just a hint for VSCode ObjectScript code completion and also a hint for a developer "what this thing is about". Compiler skips #dim lines.
go to post Evgeny Shvarov · Dec 27 Thanks for the PR with even more examples! The new version has been released!
go to post Evgeny Shvarov · Dec 26 thank you @Ashok Kumar T @David Hockenbroch both! Included your code into the new embedded python template release - here.
go to post Evgeny Shvarov · Dec 26 Thank you, @Ashok Kumar T ! Works like a charm! This is in my case:
go to post Evgeny Shvarov · Dec 26 Very cool, @David Hockenbroch ! This is what I'm getting in my case:
go to post Evgeny Shvarov · Dec 26 Found one option! ClassMethod DivideByZeroPython() [ Language = python ] { import sample import iris try: print("divide by zero=" + str(sample.dividezero(1))) except ZeroDivisionError as e: errobj=iris.cls("%Exception.General")._New(str(e),42) a=errobj.Log() print("Caught exception: " + str(e)) } This stores the error in Apps Log, but no stack (of course): Any ideas how I can store at least the class and line of code in parameters? I can provide the name and location to %Exception.General class that will be stored in the App Log.
go to post Evgeny Shvarov · Dec 23 Thanks, @John Murray ! Do you have any examples connecting both locally and remote?
go to post Evgeny Shvarov · Dec 23 I'd appreciate any example of a ready-made .code-workspace file, thank you in advance!
go to post Evgeny Shvarov · Dec 21 Interesting! Do you want to share an example of .code-workspace files and how to switch between servers?
go to post Evgeny Shvarov · Dec 20 Yes. It maybe a different thing: the format with <Export generator> is outdated and Studio together with LoadDir both support the outdated format and don't support the "new" one without the <Export> element, which is in Atelier API that VSCode is using (why do we still use this Atelier name? ) So, I'd better ask to support the new format, as the Export tag thing also has an annoying "feature" that it incudes date/time of export and this changes the file with every save/export even there were no changes.
go to post Evgeny Shvarov · Dec 20 Hi Team! Installed the extension in VSCode, installed classes via IPM zpm "install iris-oas-test-gen". Opened Swagger 2.0 spec file, clicked generate, and see the following: Looks like a connection error. I have VSCode connected to IRIS - it's in a docker contaner. Any hints how to make the extension see working IRIS?
go to post Evgeny Shvarov · Dec 20 The only "caveat" of the approach is that you should put all of the pivots and dashboards into one big class container. Even you have 100+ of them. It's like, "let's put all the classes into one big XML and store it in the repo in one file". It's OK for import/export, but not ideal for source control.
