Good morning,
First of all thanks for your help and time.
We find ourselves at a crossroads in our development journey, and we're reaching out to the community for insights and guidance regarding a critical aspect of our data management strategy.
Our current challenge revolves around the persistence of data in Globals, specifically when it comes to purging. The issue at hand is that, despite purging, data stored in Globals under the current %Persistent classes remains intact. To address this, we are contemplating a shift from %Persistent to %SerialObject for each relevant class.
Our primary concern is whether the Global continues to be in use even after making this transition. We have delved into the InterSystems documentation, particularly the section on class storage updates [1], which states that the storage definition is established during the initial compilation. However, it leaves us with uncertainties about the behavior post-compilation.
As per the documentation [2], it appears that deleting the storage definition during development and recompiling the class is suggested for a clean storage structure. Our specific question is: Will changing the class's Extends from %Persistent to %SerialObject, deleting the storage definition, and recompiling suffice to ensure that upon purging, data is automatically removed, and the Global is no longer in use?
We've also sought information from the InterSystems documentation on %Library.SerialObject [3] and a topic related created by Eduard Lebedyuk in the forum [4], but we believe your experiences and insights could provide valuable clarity on this matter.
Your expertise is highly appreciated, and we look forward to your thoughts and suggestions.
Thank you,
Thanks for your replies, time, help and support.
Yone
Open Exchange
