At this moment, when you upgrade an accept environment from version 1.61 to 1.66 for example, upgrade scripts that are linked to a specific version between version 1.61 and 1.66 are not included. I think the upgrade scripts that are linked to version 1.64 for example, should be included in the upgrade from 1.61 to 1.66 as well.
This could be accomplished by assigining the control procedure to after_upgrade_always, but this means that you need to unassign the control procedure after the upgrade, especially when you are using the control procedure template to migrate/convert data from the old structure to a new structure for example.
This is also not the ideal situation when you’re reaching for automatic deployment with an azure pipeline for example.
Hi Bram,
In the next version (2023.1), we refactored the way these upgrades work. In this version you will no longer upgrade from a version to a version, but rather upgrade from a point in time to now/current time.
This means that created upgrade scripts will be assigned to a previous (model) version, and will be reused if another database is upgraded from the same version.
In your example, upgrade from 1.61 to 1.64 and upgrade from 1.61 to 1.66 will not be any different in regards of any assigned Upgrade script.
Would that satisfy your wish?
Hey Mark,
Yes this sounds like a great solution. We’re very hyped to see the 2023.1 release with the system versioned tables!