Hi Luis,
You stand correct in that schema evolution is the responsibility of the application or solution developer. I would recommend making sure you version your solution, as you already suggested, and have a corresponding function to run the necessary conversion or evolution.
As you run your new pod/container carrying the new solution version code, you would mount your PVCs and check on the existing version of your schema in the PVC and then run the conversion.
As a schema evolution might take some time, you might want to make sure you inhibit DB activities via one of the switches we offer: https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSTU_remote_switch
HTH
- Log in to post comments