Right now In-Portal has upgrades.php and upgrades.sql files in each module, that can be upgraded. Over time we got a lot of code there that is only executed once, but distracts attention from actual last upgrade script code that needs to be written.
I'm proposing, that we return to upgrade script storage system, like it was in 4.2.0 and earlier versions of In-Portal: one file per version:
- upgrade_5.2.0-B3.sql and upgrade_5.2.0-B3.php and so on
Using php build-in function "version_compare" we can easily sort these files. But this time let's place these files in install folder sub-folder and not in install folder itself, like it was done in 4.2.0 and before.
- Alternative approach of joining
upgrades.sqlis discussed in [deployment] Incorporate "upgrades.sql" into "project_upgrades.sql" [5.2.1-RC1] discussion.
- [deployment] Using file-per-revision for Deployment Script