- Log in to post comments
User bio
Good day!
I'm running InterSystems Corporate Venture Fund and a co-founder of Caelestinus Incubator..
I love our Developer ecosystem projects Community, Open Exchange and GLobal Masters, Ideas Portal and Package Manager!
I encourage you to join our Partner Directory and Partner Portal!
I invite you to join our InterSystems startup ecosystem: InterSystems Venture Fund, Digital Health Startup Incubator Caelestinus and Startup program!
I find a great pleasure participating in this great community of like minded, helpful and open hearted people!
Would love to be connected in LinkedIn and Github!
I wish you to have a great day and find some happiness, joy and calm!
Show all
Member since Nov 10, 2015
Posts:
Replies:
It's not a matter of ResultSet availability in another namespace; it's a matter of the data you have access to in one namespace and not in another.
if you need the access to data that is available in namespace A to namespace B, there are many ways to make it work:
- map the data for namespace B via global mappings and run the query and work with the ResultSet in namespace B directly.
- Parse the resultset in namespace A, put all the results into a global that is visible in namespace B via extended syntax Access the global in namespace B directly.
- Put the results into a file on a disc or %Stream and work with them in namespace B.
- any other way that is more suitable to your task.
But reconstructing the ResultSet, which is just an object in memory suitable to access the data that is still in Namespace A, I wouldn't follow the idea.
- Log in to post comments
Well deserved, @Ashok Kumar T ! Thanks to all your contributions to this community!
- Log in to post comments
Open Exchange applications:
Certifications & Credly badges:
Followers:
Following:
Great stuff, @Guillaume Rongier !
Could you please also publish at https://openexchange.intersystems.com ?