go to post Robert Cemper · Feb 24, 2022 sorry Rich. this seems to be outdated.all examples in OEX refer to Oauth 2.0
go to post Robert Cemper · Feb 23, 2022 and that's the effective code behind Set rc=$zf(-1,cmd_" 2> """_errorfile_""" > """_outputfile_"""")
go to post Robert Cemper · Feb 23, 2022 Thanks for the hint.The review is imported from @Yuri Marx but the import flag * got lost , fixed.
go to post Robert Cemper · Feb 23, 2022 Why together ? ? ? Who wants that ? ? ? Where ? ? ?A simple MERGE ^archive(....)=^source(....) just doesn't maintain any index.this was my message
go to post Robert Cemper · Feb 22, 2022 You have a lucky design without indices. That makes life with 2 distinct globals easy.The archiving action maintaining the original ID could be achieved by a simpleMERGE from ^source to ^archive. maintenance of indices could be slightlyeffort requiring class methods.
go to post Robert Cemper · Feb 21, 2022 Sorry. it just turned out that sharing across namespaces doesn't (yet?) work with embedded Python
go to post Robert Cemper · Feb 21, 2022 I just verified that neither class nor routing mapping works with embedded Python.Not even the elementary trick to have it as a %Z* class in %SYS.This applies also to 2022.1 preview. The BUG is logged at WRC.I share your disappointment.
go to post Robert Cemper · Feb 20, 2022 Hello Peter,Like you, I have an > 40-year history with MUMPS dating back before DSM-11.Not every implementation of the global storage was effíent (no names, no finger-pointing)What you see today in IRIS is the result of continuous effort on improving performanceand storage efficiency.In past, the size of a physical disk was the limit. Today with virtual storage systems thelimit is set only by the file system used. This is a fact that InterSystems lives with since "ever". A word concerning global efficiency:Multiple experiences over years showed me that the space consumption with IRIS and its predecessor Caché was always significantly lower than with the various source DBsI was invited to migrate. With Sybase, it was rather more impressive than with others.The immediate consequence of this high efficient storage technology is the gain in speed.Also with the most modern technologies, there is still a transfer between persistent storage (aka. disk) and memory. And the less you have to transfer the faster you are. Finally, welcome to this society!Robert
go to post Robert Cemper · Feb 20, 2022 But be aware to have the method SetNamespace available also the new target namespace to be able to return !So you either map the class to Namespace %All, or name the class %ZEmbedded.Utils or similar, to make it available across all namespaces.
go to post Robert Cemper · Feb 19, 2022 Thank you for raising and extending the subject againthat got not much echo from my article Storage Considerations on large data sets published in Sep.2021
